| Can you disable SMILES conversion? [message #1168] |
Mon, 07 December 2020 12:40  |
zsolt
Messages: 4
Registered: December 2020
|
Junior Member |
|
|
a quick question on SMILES conversion: using DataWarrior with some larger datasets we noticed that SMILES conversion takes an unacceptably long time. For certain workflows it is not required for us so would like to ask it it is possible to disable it?
Another idea I am thinking as a workaround is to somehow craft a DataWarrior specific file (e.g. a .dwar) where I specify the columns containing my SMILES as plain text type - maybe then DataWarrior won't try converting it. (However I would not like to have to specify all the extra bits that are contained in the .dwar file like the position of the windows, filters etc...)
Thanks in advance,
Zsolt
|
|
|
|
|
|
| Re: Can you disable SMILES conversion? [message #1175 is a reply to message #1171] |
Tue, 15 December 2020 00:32  |
zsolt
Messages: 4
Registered: December 2020
|
Junior Member |
|
|
Thank you very much for the reply - this works, the processing is much faster indeed.
The only issue now is that when I try to set these plain SMILES strings to be on one of the axes of the 2D plot I get the error message "Column <column name> is neither a descriptor nor does it have a numerical variance" if I try to use it from a macro and it is missing from the options if I try to set it through the GUI. It makes sense not to be able to set a string as one of the axes however it seems to be possible for other string/plain text type columns - presumably because they are "descriptor"s. Is there a way for these plain-text-SMILES columns to be specified as an axis of the 2D and 3D plots?
Thanks,
Zsolt
[Updated on: Tue, 15 December 2020 00:33] Report message to a moderator |
|
|
|
| Re: Can you disable SMILES conversion? [message #1180 is a reply to message #1175] |
Sat, 19 December 2020 12:36 |
thomas
Messages: 715
Registered: June 2014
|
Senior Member |
|
|
|
In this case the 'Smiles' column is a normal text column, for which DataWarrior keeps a sorted list of available categories unless the number of different text entries exceeds 65536. As long as the number of distinct smiles values (categories) stays below that value, the column is considered to contain categories and can be assigned to an axis. Categories have a natural or user-selected order and, therefore, individual smiles can be assigned a numerical value (its position in the category list), which is used to position it on the axis. If the number of distinct values in a column is larger than 65536, then DataWarrior doesn't maintain a category list anymore. Then it cannot assign numerical values to individual smiles to position them on an axis. For efficiency reasons there must be a limit.
|
|
|
|
Search
Help
Members
Register
Login
Home
