Output files are corrupted (but not always)

[Guillaume-Blanchet]

Hi all, I report here a bug that I am facing since a few weeks and that is inconsistent accross simulations that I perform. I run simulations of Hi-sAFe through hisafer, and everything appears to be work perfectly until the file generation itself. However, when it comes to file reading, it appears that some of the generated output files contain additionnal information that hinder the possibility of reading them with hisafer.

As an example, I attached two files - one corrupted and one perfectly generated. One might observe that additionnal lines were added in the corrupted file - those lines correspond to input files (here it is code lines coming from the .tec file )

The issue is inconsistent in the sense of :

• corrupted file is not always the same :
  • if I run the simulation for a 1st time, I get for instance the "<...>_annualCells.txt" that is "corrupted"
  • on the 2nd simulation, it will be the "<...>_climate.txt"
• I had this issue for a while on two computers that I use (one under Windows at work, one under Linux at home) - now the issue appears to be fixed on my Windows computer (without any idea of the reason), but not on my Linux one...

PS : I am not sure if this is related to HisAFe itself or hisafer, so I post this issue on both github (Hisafe and hisafer) L1N30_L2N10_annualCells(corrupted).txt L1N30_L2N10_annualCells.txt

[Guillaume-Blanchet]

Link of the issue reported on the Hisafe github : https://github.com/hisafe/hisafe/issues/47 (need access right)

[kevinwolz]

Very weird! This is definitely a Hi-sAFe issue, though, not hisafer. hisafer never edits the output files - it just reads them.