Command File translator to EnSight 10

Hi folks,

as the grouping syntax has changed in EnSight 10 I’m sure many users will be faced with the problem that their old command files might fail if they do an upgrade to the latest EnSight version. We have some users with large scripts that include grouping operations so I started to think about a solution for this issue. Attached is the latest version which is still not completely finished but it seems to work fine on most command files I have used for testing. Please feel free to run the routine on your own command files and let me know if it crashes or if EnSight 10 fails on playing the translated files.

The only way I saw to get all necessary part and group info was to replay the original command files. So the original data files must be located at the directory which is included in the command file. The script will create a temporary .enc file and a .py file so the user must have writing permissions to his working directory. To start the script, please navigate to the saving path of your command files and run it with EnSight 9. The script will automatically search all .enc and .cmd files in that directory. If the routine failes on any of the found files for a reason it will create a short output message instead of translating the original command file. The translated files will be written to a new directory in the working directory witch will be named as currentyear_currentmonth_currentday_ensight10_command_files.



Download the latest update (June 2012) here.


2 thoughts on “Command File translator to EnSight 10

  1. First thing that you have to be aware of is that all your original command files that you want to translate are lying in the same directory together with the script The command files must be run-able. Means that you must have access to the original data sets and all necessary paths to open them must be included in the original command files.

    You can start the Python script by opening EnSight and go to Menu File > Command and click on the green play button. Just select the script in the file browser and it should run.

    The other way is to start Ensight directly from the command line with an argument. Open a Linux terminal or a DOS console and navigate to the directory where your Python script was saved. Now type:

    As soon as the script is finished you’ll see a new directory at your working path which is called “2012_6_5_15_57_24_ensight10_command_files” or something like that. The name starts with the current date and local time. This directory will include the translated files. If you are not sure about the location go to the EnSight menu file > command > Python. There you will see the necessary outputs.

Leave a Reply