Code center > Bugs and fixes

Large sim won't load

<< < (2/3) > >>

EricL:
You hand edited it using an editor, correct?  Sim files are super sensitive to position.  The slightest change can throw off the read frame.  The files arn't text, their binary, so they don't even break on byte boundaries.  Unless you edited the mutation details string length exactrlky right for every bot record in addition to simply deleting the mutation details strings, you will introduce read frame problems which could very well result in the program reading in a byte sequence that when cast results in a negative length.

I will see if I can resurrect the sim by overriding things in the debugger as the file is read in, but no gaurentees.  In general, you void the warrenty when you edit a sim file by hand.

EricL:
Okay, I tried, but there are other read frame issues in the file.  It's too far gone.  Sorry.

Sprotiel:

--- Quote from: EricL ---You hand edited it using an editor, correct?
--- End quote ---
No, I used a script, parsing for mutation details and copying everything else, and also modifying the mutation details length bytefield according to the actual algorithm used in VB code. Yesterday, it seemed to work for other sim files, but not today. I guess I should send you the unedited files.

EricL:
Okay.  If you have looked at the code, you know there are two mutatiuon details length fields in the file.  One is the old integer one, the other is the new Long valued one.  Your script needs to set the old one to length 1 and set the new one appropriatly.  Or, you could just use the DB program itself to save without mutation details....  

Does the unedited sim file not load?  If it does not, then yes please, compress and send that to me and I will debug that one with vigor.

Sprotiel:
It appears that I can load a previous autosave, albeit with some mutation details removed. Which is no big deal since I'm forced to remove them anyway. So case closed, I guess.
Edit : the "Fix bot radii" checkbox doesn't seem to be working properly, and I don't recall having trouble with it before the save and reload.


--- Quote from: EricL ---Okay.  If you have looked at the code, you know there are two mutatiuon details length fields in the file.  One is the old integer one, the other is the new Long valued one.  Your script needs to set the old one to length 1 and set the new one appropriatly.  Or, you could just use the DB program itself to save without mutation details....
--- End quote ---
Actually, I set the short int value, not the long one. But, for some reason, it doesn't work, which is too bad because I'm quite fond of the sort of stuff I get with my phylogenetic tree script (see attachment) and I hoped to be able one day to strip mutation details without losing the information in them.

Navigation

[0] Message Index

[#] Next page

[*] Previous page