Hi Sergio, The log files corresponding to the sessions where you ran into problems may be helpful. You can find them under ~/.Seg3D - the files are data and time stamped. It's possible that the session information and database files are getting corrupted when Seg3D fails to save your sessions. It may also be useful to send the sessions and database files from the project that is failing to save. If you look in the directory in which your projects are being saved, you'll see directories with the naming pattern *.seg3dproj. It should be laid out as follows: yukon:bin.debug ayla$ ll ~/test.seg3dproj/ total 8 drwxr-xr-x@ 7 ayla sci 238 Oct 8 2012 . drwxr-xr-x+ 140 ayla sci 4760 Aug 16 15:27 .. drwxr-xr-x 4 ayla sci 136 Oct 10 2012 data drwxr-xr-x 5 ayla sci 170 Oct 10 2012 database drwxr-xr-x 17 ayla sci 578 Jan 10 2013 inputfiles drwxr-xr-x 4 ayla sci 136 Oct 10 2012 sessions -rw-r--r-- 1 ayla sci 1065 Oct 10 2012 test.s3d You can find the session and database files under database and sessions: yukon:bin.debug ayla$ ll ~/test.seg3dproj/database/ total 80 drwxr-xr-x 5 ayla sci 170 Oct 10 2012 . drwxr-xr-x@ 7 ayla sci 238 Oct 8 2012 .. -rw-r--r-- 1 ayla sci 4096 Oct 10 2012 notes.sqlite -rw-r--r-- 1 ayla sci 25600 Oct 10 2012 provenance.sqlite -rw-r--r-- 1 ayla sci 8192 Oct 10 2012 sessions.sqlite yukon:bin.debug ayla$ ll ~/test.seg3dproj/sessions/ total 56 drwxr-xr-x 4 ayla sci 136 Oct 10 2012 . drwxr-xr-x@ 7 ayla sci 238 Oct 8 2012 .. -rw-r--r-- 1 ayla sci 9211 Oct 8 2012 1.xml -rw-r--r-- 1 ayla sci 13844 Oct 10 2012 2.xml In the meanwhile, have you tried saving your work in a new project (using File -> Save Project As)? Ayla On Aug 16, 2013, at 4:01 AM, Sergio Vera wrote:
|
Archive powered by MHonArc 2.6.16.