GEO_REF bias value reading chokes on 2nd character
Closed this issue · 2 comments
As demonstrated with the attached input/output, the program aborts when called with a value field longer than 1 character
(not included are working runs when 1-char value is accepted).
This has already been fixed in the latest github pull. See #152 .. I just ran your example without any problems on linux.
The development version isn't flagging an error anymore, however it does state that By default, no restraining force will be used after reading in the geometry on my development machine (Mac), and it doesn't seem to be recognizing the constraining force in the calculation itself right now. The restraining force seems to be parsed and functioning correctly in the output reported by @flatstik on a Linux machine. I need to fix the source of this discrepancy before this issue can be considered resolved.