DURATION() can corrupt database

[GoogleCodeExporter]

What steps will reproduce the problem?
Is a complex analysis so haven't attached it at present - can send offline if 
necessary.

Calling DURATION() in READ mode gives the error:
dio.c: 69 => Invalid master id

Trying to run Solfec again in READ mode gives the error:
pbf.c: 238, Unhandled error: PBF index file corrupted

I'm getting round this by backing up all results files before trying anything 
... is there a simpler way, e.g. just backing up the smaller .idx.N files?

Original issue reported on code.google.com by steve.br...@atkinsglobal.com on 27 Nov 2012 at 4:31

[GoogleCodeExporter]

OK this might help a bit. A simplified version of the script is:

solfec = SOLFEC('DYNAMIC', STEP, 'out')
solfec_modal = SOLFEC('DYNAMIC', STEP, 'modal')
modalbdy = BODY(solfec_modal, 'FINITE_ELEMENT', COPY(mesh), bulkmat, 
label=some_label)
modaldata = MODAL_ANALYSIS(modalbdy, nmodes, modal_data_path, abstol=1E-13)
bdy = BODY(solfec, 'FINITE_ELEMENT', mesh, bulkmat, label=some_label, 
form='RO', modal=modaldata)
RUN(solfec, slv, STOP)

I do this so that the modal results go into a separate database, but maybe this 
is a bad idea?

I'm running this as advised:
a) running the modal analysis in serial (using -v so I don't run the actual 
analysis)
b) running the dynamic analysis in parallel
I'm finding I have to delete /out after a) else b) will run ok but then also 
throws a "PBF corrupted error"

I'm finding that I can at least "fix" the database so I can still view the 
results after I get a PBF index error from the postprocessing originally 
described by deleting the .dat, .idx and .lbl files in the /modal directory - 
all of which are 0-size.  I also note that the Viewer will generate these if 
it's closed via the "X" button (in which case you get a PBF error on trying to 
reopen it) but won't if it's closed via the menu.

None of this will fix the "Invalid master id" error but I suspect it might give 
a handle on what's going wrong with thsse PBF index errors.

Original comment by steve.br...@atkinsglobal.com on 27 Nov 2012 at 5:34

[GoogleCodeExporter]

Check if still occurs after fixing the set usage.

Original comment by t.kozi...@gmail.com on 28 Feb 2013 at 3:04

[GoogleCodeExporter]

Since we are now moving to the HDF output, I am wondering what is the status of 
this issue. Do you think looking into this is still needed?

Original comment by t.kozi...@gmail.com on 7 Sep 2013 at 10:32

[GoogleCodeExporter]

I would close it given not much use of modal method at the moment and the 
change to HDF.

Original comment by steve.br...@atkinsglobal.com on 9 Sep 2013 at 9:44

[GoogleCodeExporter]

Original comment by t.kozi...@gmail.com on 9 Sep 2013 at 11:17

• Changed state: WontFix