One common situation is to have multiple files referring to the same simulation in different time domains, and want to create a single animation through time with them.
For some data formats, there is the possibility to patch the files together in a single file, as for example for the cfx data format, or the EnSight Case Gold dataset (edit the Time information and files referenced).
But for the majority of data format this is not possible, and therefore you will need to get to the same result using EnSight.
Let's say for example that you have two case files, with the first one containing the simulation from timestep 0 to timestep 20, and the second one with the simulation from timestep 20 to timestep 40, as in the attached example datasets.
If you load both of them into EnSight, you'll find that the time dialog shows steps 0 - 40.However when you play through time, there is always geometry from timestep 20 that displays along with the animation. This is because when the time is less than or equal to 20, case 2 shows, by default, the geometry at timestep 20, and when the time is greater than or equal to 20, case 1 shows timestep 20. So, simply loading both datasets does not work.
Here there are three different approaches that you can take, based on which is your exact target and which version of EnSight you have.
a. Load up one model, create an animtion from time t=0 to t=20. Save off an animation file (animation1.avi for example). Also save a Context file at this point. This "context" file will provide you with the ability to restore to this same view/color/orientation.
b. Load up the second model. Then, File -- > Restore -- > Context file, and restore the context file that you saved from the first model. You may want to start at 1st timestep, rather than the 0th timestep (since time step 20 is included in both datasets).
c. Save off animation (animation2.avi).
d. Use EnVe (from CEI), to sew the animation into one. You can open up EnVe, and simply load up animation1.avi and animation2.avi. You can then save off a new file (animation_whole.avi), which is those two sewn front to back.
a. Load up both models into EnSight (on second dataset read, select "keep loaded data").
b. Make Case 2 invisible. Re-adjust the time limits to that of case 1 (0-20). Play through time, and record off the animation (animation1.avi)
c. Now, make Case 2 invisible, and Case 1 visible. Adjust the time limits to that of case 2 (21-40). Play through time, and record off the animation. (animation2.avi)
d. Use EnVe from CEI to sew animation back into one.
a. Load up both models into EnSight (on second dataset read, select "keep loaded data")
b. COLOR all parts by a variable (let's say pressure for example).
c. Open the Timeset details of the Time Object window. At that point you will see four time sets: two for each case, one for the geometry, one for the variables. Select the variables timeset, and choose the pressure variable, and choose for the right side, undefined if to the right of definition. That way variables will be undefined if the time value is to the right (greater) than the timeset times. Do the same for case 2, except it's to the left (less than) that you want variables undefined.
d. Now click on the color wheel, and choose Palette -- > Options. In the "Display undefined" option, change that to "make invisible".
Now the variable will be undefined and invisible when out of it's time.
e. Play through full time. No further modifications/operations needed.
Here some suggestions on which option can be the ideal one for you:
1. Only have EnSight Desktop (you can not load multiple datasets), use Option 1.
2. You have EnSight Standard, and want flexibility in coloring, use Option 2.
3. You have EnSight Standard, and are coloring all parts by a variable, and want a single animation file (or EnLiten file), you should be using option 3.
4. You need EnLiten Scenario file. Option 3.
Option 3 relies on using the Color Palette to "Hide" parts when their variable is undefined. This works well, as long as you are always coloring by a variable. If you want something "solid" color, this will not work.
Option 1 is quite basic, and perhaps a bit "old-school", but is generally applicable and useful when you want flexibility.
Option 2 is slightly easier to use, but has some of the same restrictions of option 1.