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
In #1493, we added sourmash_args.SaveSignaturesToLocation(...) to support a wide variety of output formats.
In #1891, we are adding the ability to read manifest files, as output by sourmash sig manifest.
Per the motivation in #1365, it would be nice to be able to output these manifest files as the result of searches etc. -o could maybe support that, under certain conditions - in particular, that all signatures were loaded from identifiable locations (so, not stdin; anything else?)
One concern is that these manifest files would not necessarily be that portable or relocatable, depending on whether they contained relative paths or abspaths - both are problems. So it could be a buyer-beware kind of situation to support @bluegenes -like people, that is, expert users.
The text was updated successfully, but these errors were encountered:
in #1891, I'm adding sourmash sig check --output-manifest-matching which will output entries that match to a picklist in manifest format. Right now it's specific to this command, but we'll be using it for #1671 so if it proves out there we can revisit and implement more broadly.
In #1493, we added
sourmash_args.SaveSignaturesToLocation(...)
to support a wide variety of output formats.In #1891, we are adding the ability to read manifest files, as output by
sourmash sig manifest
.Per the motivation in #1365, it would be nice to be able to output these manifest files as the result of searches etc.
-o
could maybe support that, under certain conditions - in particular, that all signatures were loaded from identifiable locations (so, not stdin; anything else?)One concern is that these manifest files would not necessarily be that portable or relocatable, depending on whether they contained relative paths or abspaths - both are problems. So it could be a buyer-beware kind of situation to support @bluegenes -like people, that is, expert users.
The text was updated successfully, but these errors were encountered: