You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've found that when attempting to train a SOM initialized with the a previous SOM output file that there will be readSOM errors raised. Testing the code out I think that the std::getline is getting into an error state as it unsuccessfully searches for the # END OF HEADER string in a file without one. If a file does not contain the # END OF HEADER it will eventually get to the end of a file and attempt to read in a new line, at which point an error is encountered and subsequent seekg will no longer work.
This behavior can be seen by inspecting the is.eof() bit before and after the scan of the header is performed.
Fixing it requires a is.clear() to be added. I am not sure if the problem persists in other areas of the code.
The text was updated successfully, but these errors were encountered:
I noticed that after I fixed the readSOM bug. Started wondering why I only saw it with the SOM and not images. If I read that first I would have saved about an hour of debugging!
This was introduced in #17 .
I've found that when attempting to train a SOM initialized with the a previous SOM output file that there will be
readSOM
errors raised. Testing the code out I think that thestd::getline
is getting into an error state as it unsuccessfully searches for the# END OF HEADER
string in a file without one. If a file does not contain the# END OF HEADER
it will eventually get to the end of a file and attempt to read in a new line, at which point an error is encountered and subsequentseekg
will no longer work.This behavior can be seen by inspecting the
is.eof()
bit before and after the scan of the header is performed.Fixing it requires a
is.clear()
to be added. I am not sure if the problem persists in other areas of the code.The text was updated successfully, but these errors were encountered: