Closed jimallman closed 10 years ago
oops. I thought that I had tested that. I'll look into it today. Should be a quick fix (famous last words)
Fixed. Thanks Jim, that was a scary bug (see https://github.com/mtholder/ncl/commit/6fb4c1895bc222a696f1050386e51a6862898b1a for details) that would lead to undefined behavior. Introduced when I started supporting user-specification of NeXML ids counter.
For other NCL users: This bug only affect writing of NeXML. No other NCL functions were involved. So this was a bug in the example code, not the library part of NCL.
I'm calling NCLconverter from the Open Tree curation app, sending the test file avian_ovomucoids.nex to import its trees. It's then called with these options:
Note that the next available node id is 505. When the NexSON is returned with added trees, there are dozens (not hundreds) of duplicate ids: 505, 506, 509, 636, ... reported in the JS console.
Could the duplication be happening because there are multiple trees in this file?