<@U01SBMJT5BP> I have come into this issue. suppos...
# xyce
s
@Eric Keiter I have come into this issue. suppose Xyce is running a simulation (assume for example a transient analysis, but the issue is general). Xyce is writing the raw file as simulation advances. If I terminate the program (with SIGTERM signal, not SIGKILL signal which can not be handled by the application) Xyce does not update the raw file with the number of points saved so far. This should be easy to do. while Xyce is running the
No. Points
line in the raw file is left blank ( there is no second field with the number of points). The reason is clear, number of timesteps is only known at end of simulation. When simulation completes Xyce adds the number to the
No. Points
line at the beginning of the raw file (there are probably padding blanks to allow inserting the number without shifting the whole file data). My request is to do the same when a SIGTERM signal is catched. The same issue happens if I interrupt Xyce with Ctrl-C (SIGINT signal). The raw files resulting from an interrupted simulation are not easy to read, since the reader must first analyze the whole file and calculate the points saved. The No. Points is expecially useful in binary raw files, so the application reading it can immediately allocate the data structure (nvars * npoints*sizeof(double))