This issue comes up in testing the new unit tests I added with custom settings and parameter combinations that were not exposed the way they are in the command line versions of GTFold. It is likely that fixing 1-2 single bugs will fix the multitude of failing tests. The plan is to get behavior that is consistent with the output of historical GTFold. It is on my TODO list. Note that many standard combinations available in other tests ARE passing at the moment!