@Robin-Rounthwaite points out that, if you build a graph with Cactus, it makes you specify a reference assembly name, and you come out with reference-sense paths scoped to that assembly.
If you build a graph from the same FASTA with vg construct, it just uses the FASTA IDs as path names, and the path names then do not match the ones created by Cactus.
We should support (or probably require?) using a sample/assembly name with vg construct, to stop people from making graphs with incompatible path coordinate spaces.
@Robin-Rounthwaite points out that, if you build a graph with Cactus, it makes you specify a reference assembly name, and you come out with reference-sense paths scoped to that assembly.
If you build a graph from the same FASTA with
vg construct
, it just uses the FASTA IDs as path names, and the path names then do not match the ones created by Cactus.We should support (or probably require?) using a sample/assembly name with
vg construct
, to stop people from making graphs with incompatible path coordinate spaces.