remedy for ensight
 

why is it very often my pc crashed when exporting results into Ensight? Is there a known way to fix this problem??

Re: remedy for ensight
 

Which version of Prostar are you using? Standard release of v3.26 does have a bug in it causing Prostar to crash when writing EnSight files. I believe that patch 11 to v3.26 solves this problem.

Re: remedy for ensight
 

ok thanks for that info! it's v3.26.004.

Strangely i had lesser problem on this version to write for Ensight a few weeks back.

Re: remedy for ensight
 

Hi,

I've had in the past also similar problem. It's a memory problem. if you over define MAXCUT MAXSC1 MAXSC2 and MAXSC3. You don't really know exactly how much more memory prostar can still function properly (without crashing), because the prostar keeps telling you to increase the memory without saying "At least xxx"

since then, I manage to write my ensight output manually on the command. It works....!! almost always...

just type HELP ENSI on the command line, then you find out how to do it manually. It gives you also an example.

Cheers, Reza

Re: remedy for ensight
 

It also helps to be on a later version of Prostar. Early versions of 3.26 were a problem within the ensi routine in Prostar. V3.26 patch 11 solves most all of the problems experienced previously. Definitely getting comfortable with the setwrite and the ensi commands, you can write out exact what you want.

Re: remedy for ensight
 

ok this sounds nice, so i should just type setwrite in the i/o window? what other commands should i use in there?

Re: remedy for ensight
 

You have several options: 1. You can use the NavCetner -->export --> to EnSight. This is quite easy and straight forward, but also not a lot of control. I would use this simple method first, and see if this gives you what you want. 2. Alternatively, you can use the "setwrite" command to build a setfile containing the parts that you want to have in EnSight. You can then use the "ensi" commands commands in combination with getc or getv commands (and operate commands) to generate the variables that you would like to export to EnSight. This is a slightly more involved process, but allows you ultimate flexibility in parts and variables written to EnSight. Check out : http://www.ensight.com/screencasts/S...ate_Export.htm