openmolecules.org Forum: Bug Reports » > and < signs not interpreted in 6.0.0

Home » DataWarrior » Bug Reports » > and < signs not interpreted in 6.0.0

Show: Today's Messages :: Polls :: Message Navigator

Re: > and < signs not interpreted in 6.0.0 [message #2101 is a reply to message #2100]

Sat, 13 January 2024 20:18

nbehrnd
Messages: 233
Registered: June 2019

Senior Member

In continuation with DW 06.00.00, I created a new array: the first column with three random molecules (DW generated), the second column added with Data -> Add empty columns, where I selected "text" as category. Manually, I added the strings `>2000`, `55.6`, and `20` to the cells as a test property (cf. attached .dwar and `dw_screenphoto_01.png`). The subsequent addition of a third column by Data -> Add Calculated Values used a function of

if(test_property>20, "big", "small")

proceed smoothly. In your case application, do you equally have the automatic assignment of the column type enabled? This is based on the observation the intended computation is going to fail if the second column (still/accidentally) is set to the level of `text` -- regardless if `force categories` is activated, or not. Subsequent adjustment of the second column, then re-run by right-click on the third column and "update formula and recalculate" adjusted the results.

However: I assumed a right-click on the third column and subsequent "Re-Calculate All Columns" would be more helpful for a global update of the array of maybe multiple columns of calculated values. Hélàs no, it replaced the original entries in the second column by the results of my formula, and yielded the "NaN" indicator in the third column (dw_screenphoto_03.png). This observation is less intuitive to me.

Regards,

Norwid

Attachment: Random_Molecules.dwar
(Size: 1.25KB, Downloaded 216 times)
Attachment: dw_screenphoto_01.png
(Size: 29.37KB, Downloaded 141 times)
Attachment: dw_screenphoto_02.png
(Size: 31.26KB, Downloaded 131 times)
Attachment: dw_screenphoto_03.png
(Size: 13.68KB, Downloaded 142 times)

[Updated on: Sat, 13 January 2024 20:19]

Report message to a moderator

[Message index]

		> and < signs not interpreted in 6.0.0 By: mcmc on Thu, 11 January 2024 12:19
		Re: > and < signs not interpreted in 6.0.0 By: nbehrnd on Thu, 11 January 2024 23:42
		Re: > and < signs not interpreted in 6.0.0 By: mcmc on Fri, 12 January 2024 12:03
		Re: > and < signs not interpreted in 6.0.0 By: nbehrnd on Sat, 13 January 2024 20:18
		Re: > and < signs not interpreted in 6.0.0 By: mcmc on Wed, 17 January 2024 10:18
		Re: > and < signs not interpreted in 6.0.0 By: thomas on Sat, 20 January 2024 15:02
		> sign properly interpreted, but '2;3' is interpreted as text, not numercal By: mcmc on Tue, 30 July 2024 12:11
		Re: > sign properly interpreted, but '2;3' is interpreted as text, not numercal By: nbehrnd on Tue, 30 July 2024 19:31
		Re: > sign properly interpreted, but '2;3' is interpreted as text, not numercal By: mcmc on Wed, 31 July 2024 09:52
		Re: > sign properly interpreted, but '2;3' is interpreted as text, not numercal By: thomas on Wed, 31 July 2024 14:51
		Re: > sign properly interpreted, but '2;3' is interpreted as text, not numercal By: mcmc on Wed, 31 July 2024 17:50

Previous Topic:	Extract fragment
Next Topic:	Data warrior crash after Mac OS update

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Thu May 15 14:26:43 CEST 2025

Total time taken to generate the page: 0.03366 seconds