3DNA Forum

Welcome => Bug reports => Topic started by: edeveaud on February 11, 2019, 11:23:17 am

Title: x3dna-v2.4 :: checks for x2dn-v2.3 for homedir
Post by: edeveaud on February 11, 2019, 11:23:17 am: looking at get_3dna_homedir in app_fncs.c

when X3DNA env var not defined, it set homedir to $HOME/x3dna-v2.3/ or $HOMEDRIVE/x3dna-v2.3/
Title: Re: x3dna-v2.4 :: checks for x2dn-v2.3 for homedir
Post by: xiangjun on February 11, 2019, 11:58:50 am: Hi edeveaud,

Thanks for reporting this issue.

Presumably, the X3DNA environment variable should always be set. Nevertheless, since the current version of 3DNA is v2.4, the out-of-date v2.3 folder should be fixed. Please check 3DNA v2.4.1-2019feb11 where v2.3 has been corrected to v2.4.

Best regards,

Xiang-Jun
Title: Re: x3dna-v2.4 :: checks for x2dn-v2.3 for homedir
Post by: xiangjun on February 26, 2019, 11:56:50 am: Quote
looking at get_3dna_homedir in app_fncs.c

when X3DNA env var not defined, it set homedir to $HOME/x3dna-v2.3/ or $HOMEDRIVE/x3dna-v2.3/

As a follow-up, I've simplified function get_3dna_homedir() in app_fncs.c in 3DNA v2.4.2-2019feb26. Now the X3DNA environment variable must be set. The code for checking 3DNA distribution from the home directory has been removed. This feature was added from early on, including the widely distributed 3DNA v1.5. From my memory, however, it has been rarely used. Moreover, since v2.1, the x3dna_ensemble Ruby script requires the setting of ENV['X3DNA'].

Xiang-Jun