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
The local database in cfm-id and metfrag seems very similar. But its csv in one and tsv in the other. Maybe it would be good to have this consistent. I would prefer tsv since InChI contains commas (question would be if this works anyway with csv if there are additional commas). Then the same input can easily be used in both files (ie the metfrag input can be used in cfm-id - since the first columns are the same)
Maybe we should allow omitting InChI or SMILES (in the python sources there is a TODO anyway). Due to the use of the python wrapper we are free to define the format as we wish. Possibilities:
Allow to keep one column empty (maybe this is possible anyway)
Make column 3 inchi/smiles .. let the python check for startswith("InChi")?
Detect by column header
The text was updated successfully, but these errors were encountered:
The local database in cfm-id and metfrag seems very similar. But its csv in one and tsv in the other. Maybe it would be good to have this consistent. I would prefer tsv since InChI contains commas (question would be if this works anyway with csv if there are additional commas). Then the same input can easily be used in both files (ie the metfrag input can be used in cfm-id - since the first columns are the same)
Maybe we should allow omitting InChI or SMILES (in the python sources there is a TODO anyway). Due to the use of the python wrapper we are free to define the format as we wish. Possibilities:
The text was updated successfully, but these errors were encountered: