Closed rlorigro closed 2 years ago
Sadly we do not have a good way to report GFA format errors. In your case you're having invalid GFA tags, e.g.:
CL:z:#1baf1b
Note that z
is a not a valid tag type (see https://github.com/GFA-spec/GFA-spec/blob/master/GFA1.md#optional-fields for more information)
OK. Just to clarify, I think the original bandage created this tag during the save visible graph to GFA
operation. It probably cached the colors from a CSV I loaded
Does it make sense to make this backwards compatible to the extent that it does not crash during loading? Even if it ignores the tag
Well, in the reality the invalid lines are dropped. It's the error reporting that takes time as it tries to print all these long segment lines with error location, etc. to stdout.
Hi,
This GFA fails to load in BandageNG, but loads within seconds in original Bandage: https://rlorigro-public-files.s3.us-west-1.amazonaws.com/gfase/paolo_ul_guppy6_run14/test_subset/run14_uul_test_subset.gfa
It contains 1436 nodes, totaling 263Mbp
Thanks