File .sim~

sarav · July 24, 2009, 07:55

Hi everybody,
I would like to know how I can set starrccm+ in order to NOT CREATE the .sim~ file when I save a simulation.
I don't know if it is possibile.
Thanks

kyle · July 24, 2009, 16:35

It would be pretty dangerous to not save the .sim~ file. What if you ran out of disk space while saving? What if you were saving to a remote disc and the connection gets interrupted? You would lose everything. Disc space is much cheaper than having engineers do work twice.

Maddin · July 27, 2009, 06:07

Only delete them after the simulation is closed.
I had destroyed some sim file with deleting them before saving and closing the ".sim" filme.

f-w · July 28, 2009, 21:01

Hopefully it'll be an option in a future release, which I'm requesting.

sarav · August 4, 2009, 04:02

Quote:

Originally Posted by kyle

It would be pretty dangerous to not save the .sim~ file. What if you ran out of disk space while saving? What if you were saving to a remote disc and the connection gets interrupted? You would lose everything. Disc space is much cheaper than having engineers do work twice.

My problem is that on the cluster I've to use there is not enough memory and I can't delete anything!

sarav · August 4, 2009, 04:06

Quote:

Originally Posted by f-w

Hopefully it'll be an option in a future release, which I'm requesting.

Ok,thanks!
I would need this function now.....

Maddin · August 4, 2009, 04:36

Save it local and then send it to the cluster?!

sarav · August 4, 2009, 11:26

Quote:

Originally Posted by Maddin

Save it local and then send it to the cluster?!

The problem is saving the solution file on the cluster.
On it, there is memory enough for the file.sim created on the lab's computer, but there is not enough memory to save the file.sim (with the solution) and the file.sim~ after the simulation has run!

aerospaceman · November 18, 2009, 20:43

It is great to know that other people also have this problem.

What exactly is this blasted .sim~ file?

It seems to be created automatically and takes up a huge amount of memory.

Any help would be great.

Thanks.

kyle · November 18, 2009, 21:47

The .sim~ file is the backup file. This is not unique to Star-CCM+, many programs do this. Most text editors save a backup copy with a ~ suffix, Prostar saves *.bak file, even MS Office applications save a backup file.

When you save the simulation, the previous saved file is moved to *.sim~ and a new file is written at *.sim. If you were to turn this off, what would happen if there were a problem while saving? What would happen if you ran out of disk space while saving? You would have lost your only copy of the simulation. Even if you could turn this off, you would not want to. Disk space is extremely cheap.

Maddin · November 19, 2009, 04:51

MS Office often didn't create a backup file which is 1-2GB...

kyle · November 19, 2009, 12:40

It creates a backup that is the same size as the document. CFD simulations just happen to be several gigabytes.

Maddin · November 19, 2009, 13:17

Make a big mesh, save it. Then make some steps and you have the problem when your linux account don't allows much more space.

aerospaceman · November 20, 2009, 21:33

Right, thanks a lot Kyle.

So essentially the sim~ file is the second last version to be saved, is that correct?

This make a lot of sense.

Joel George · May 15, 2021, 03:24

I recently did my tutorial in starccm+. It was a simulation of a flow over a backward facing step. I imported the geometry from solidworks, applied b.c's and also did post processing. At the end I saved it and closed my starccm+.

Later on when I opened the .sim which I saved, there is nothing displayed on the graphics display area. The geometry, regions, continua, everything is showing in the tree. But the geometry, post processed results are not shown in the graphics window

Can anyone help me this.
Thanks in advance.

July 24, 2009, 07:55	File .sim~	#1
sarav New Member Join Date: Jul 2009 Posts: 25 Rep Power: 17	Hi everybody, I would like to know how I can set starrccm+ in order to NOT CREATE the .sim~ file when I save a simulation. I don't know if it is possibile. Thanks

July 24, 2009, 16:35		#2
kyle Senior Member Join Date: Mar 2009 Location: Austin, TX Posts: 160 Rep Power: 18	It would be pretty dangerous to not save the .sim~ file. What if you ran out of disk space while saving? What if you were saving to a remote disc and the connection gets interrupted? You would lose everything. Disc space is much cheaper than having engineers do work twice. Bali and BlueA like this.

November 18, 2009, 20:43	What is this .sim~ file?	#9
aerospaceman Member Join Date: Nov 2009 Posts: 43 Rep Power: 16	It is great to know that other people also have this problem. What exactly is this blasted .sim~ file? It seems to be created automatically and takes up a huge amount of memory. Any help would be great. Thanks.

May 15, 2021, 03:24	How do I open a .sim file in starccm.?	#15
Joel George New Member Joel Join Date: May 2021 Posts: 1 Rep Power: 0	I recently did my tutorial in starccm+. It was a simulation of a flow over a backward facing step. I imported the geometry from solidworks, applied b.c's and also did post processing. At the end I saved it and closed my starccm+. Later on when I opened the .sim which I saved, there is nothing displayed on the graphics display area. The geometry, regions, continua, everything is showing in the tree. But the geometry, post processed results are not shown in the graphics window Can anyone help me this. Thanks in advance.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
[swak4Foam] GroovyBC the dynamic cousin of funkySetFields that lives on the suburb of the mesh	gschaider	OpenFOAM Community Contributions	300	October 29, 2014 19:00
Changing the grid on the same set-up	Katya	FLUENT	7	October 8, 2009 17:31
Compilation errors in ThirdPartymallochoard	feng_w	OpenFOAM Installation	1	January 25, 2009 07:59
ParaView Compilation	jakaranda	OpenFOAM Installation	3	October 27, 2008 12:46
FoamToVTK and MayaVi	alexandrepereira	OpenFOAM Post-Processing	57	August 11, 2008 05:15

July 27, 2009, 06:07		#3
Maddin Senior Member Join Date: Mar 2009 Posts: 260 Rep Power: 18	Only delete them after the simulation is closed. I had destroyed some sim file with deleting them before saving and closing the ".sim" filme.

July 28, 2009, 21:01		#4
f-w Senior Member Join Date: Apr 2009 Posts: 159 Rep Power: 17	Hopefully it'll be an option in a future release, which I'm requesting.

August 4, 2009, 04:36		#7
Maddin Senior Member Join Date: Mar 2009 Posts: 260 Rep Power: 18	Save it local and then send it to the cluster?!

November 18, 2009, 21:47		#10
kyle Senior Member Join Date: Mar 2009 Location: Austin, TX Posts: 160 Rep Power: 18	The .sim~ file is the backup file. This is not unique to Star-CCM+, many programs do this. Most text editors save a backup copy with a ~ suffix, Prostar saves .bak file, even MS Office applications save a backup file. When you save the simulation, the previous saved file is moved to .sim~ and a new file is written at *.sim. If you were to turn this off, what would happen if there were a problem while saving? What would happen if you ran out of disk space while saving? You would have lost your only copy of the simulation. Even if you could turn this off, you would not want to. Disk space is extremely cheap.

November 19, 2009, 04:51		#11
Maddin Senior Member Join Date: Mar 2009 Posts: 260 Rep Power: 18	MS Office often didn't create a backup file which is 1-2GB...

November 19, 2009, 12:40		#12
kyle Senior Member Join Date: Mar 2009 Location: Austin, TX Posts: 160 Rep Power: 18	It creates a backup that is the same size as the document. CFD simulations just happen to be several gigabytes.

November 19, 2009, 13:17		#13
Maddin Senior Member Join Date: Mar 2009 Posts: 260 Rep Power: 18	Make a big mesh, save it. Then make some steps and you have the problem when your linux account don't allows much more space.

November 20, 2009, 21:33		#14
aerospaceman Member Join Date: Nov 2009 Posts: 43 Rep Power: 16	Right, thanks a lot Kyle. So essentially the sim~ file is the second last version to be saved, is that correct? This make a lot of sense.