You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
then all sequences in seqs.fasta, even those not in placements.jplace, will also be classified. This is just a bit unexpected, and is probably not what the user wants. Some options might be some combination of: a) raise an error; b) ignore the extra sequences; c) keep the current behavior but describe it in the docs. A gold-plated solution would be an error unless an option like --ignore-extras is provided.
The text was updated successfully, but these errors were encountered:
Sorry for the surprise. This shouldn't be hard-- it comes down to this merge function. I'm not so fond of the gold-plated solution because I don't like options that only make sense when other options are used. Which of the others do you think would be best?
If we were going to do (b), would you suggest taking the intersection of the sequences supplied in the jplace file and those in the NBC file?
I think that taking the intersection would be a good solution. Perhaps with a warning about any sequences that are missing from one source or the other?
If we run
then all sequences in seqs.fasta, even those not in placements.jplace, will also be classified. This is just a bit unexpected, and is probably not what the user wants. Some options might be some combination of: a) raise an error; b) ignore the extra sequences; c) keep the current behavior but describe it in the docs. A gold-plated solution would be an error unless an option like --ignore-extras is provided.
The text was updated successfully, but these errors were encountered: