How to tell exactly what causes a restart to recalculate modes?

Question

I have an existing DBALL/MASTER that I want to reuse. I built a few restart jobs and they ran great, reusing the modes and taking minutes instead of hours to solve. Then I did something wrong and the restart no longer works. The FMS is unchanged but the CC and BULK entries for the 111 and 112 do change. I ran with DIAG 56 on both the old (working) and new (not working) jobs. The *56* statements have something like this:

*56* The following parameter(s) force execution (Name : TYPE'd? Y or N : Position): NOGEOM2 :N: 1

*56* The following parameter(s) force execution (Name : TYPE'd? Y or N : Position): OLDSEQ1 :N: 1

But I don't really know how to interpret all of them.

In the end I found the problem in the CC. I am hopeful there's a direct way to get Nastran to tell me what caused the recalculation.

Sanjay Patel · Accepted Answer

Nastran does not tell you specific entry which would force the execution. But you do get the messages such as the following which would indicate the Record that was changed. For example following indicate THLDSET record was changed.

Which you can then look into DMAP module dictionary to determine what it refers to. And you will find the following indicating Thermal load set entry was changed. I hope this helps.