Error opening Ensight .case files after multiple restarts with smaller timesteps

    • SHerrera

      Hi all.

      I'm running System Coupling on a Linux-Based HPC. I've been restarting my cases with smaller timesteps each time but recently I have found I can't open either results.case file due to the following error. This problem only occurs in some cases, others open normally.

      Has someone encountered this and found a solution?


      Connection accepted.

      This is EnSight Server 2021 R2 (5/25/2021) build: 5288b459f release-21.2

      ---- -- ------- ======

      Running on computer: , , pid: 31192


       Using environmental variable TMPDIR  

      --> TMPDIR = /scratch/7506554

      Log Detected 12 CPU core(s), 6 maximum parallel threads.


      Found 2 Casefiles using 'scan' method specified in the .mcf file.

      Error ERROR: Error> {s1:1} verify_increasing_times() in timesets.c:601 

           of EnSight Server 2021 R2:

      Error ERROR: Error sequencing data.

      Error ERROR: Descending/duplicate ordered time values: t[219:218]={0.3,0.3}

      Error ERROR: 

      Error ERROR: Error> {s1:1} readensight_casefile() in resu.c:1283 

           of EnSight Server 2021 R2:

      Error ERROR: Error sequencing data.

      Error ERROR: initializing time-set spans using case data format

      Error ERROR: 

      UDW Info: server has 5 UDWs.

      Error loading parts. Please check console window for details.

    • Murari Iyengar
      Ansys Employee
      This error occurs when you stop/restart a transient simulation and the .encas files get overwritten. In some instances, the .encas file gets modified and does not have all the timestep files/data included in it. It can also occur when you transfer the files midway through a calculation from one location to another and some of the timestep data gets lost along the way. As good practice, I recommend creating a new file for each simulation and avoiding changing the file location midway through the simulation.
Viewing 1 reply thread
  • You must be logged in to reply to this topic.