On 11 October 2015 at 19:32, Sze Chan <samuelsw.c...@mail.utoronto.ca> wrote: > Hello, > > > While I was setting up my modelfree analysis in the GUI automated protocol , > I received the error in the controller: > > > RelaxWarning: comparison to `None` will result in an elementwise object > comparison in the future. > > > After loading my data, setting dipolar interactions, setting CSA relaxations > and setting the isotopes but before execution of the analysis. > > > I'm not sure what happened to cause the warning, but when the modelfree > analysis is running, each successive round of optimization in each model does > not compare to the previous round, instead it would always compare each > optimized chi-square value to 'none' such as in round 21 of the oblate model: > > > Storing the optimisation results for the spin > '#LARA_N_term_no_helixFH_reg_mol24:358@N', the optimised chi-squared value is > lower than the current value (283.50425283 < None). > > > Even though I'm guessing it should refer to a previously optimised value? > > > During the analysis it would go through the default 30 rounds of optimisation > for each global model but not reach convergence. > > > I was wondering how I can remedy this or at least create a log file so I can > make my problem more clear.
Hi Sam, I would suggest running relax with these options: $ relax --gui --log relax_warning.log --traceback This will start the GUI, send all output into a 'relax_warning.log' file, and produce highly detailed RelaxError and RelaxWarning messages pointing to the exact place in the code where the problem occurred. Then exit relax once this warning first occurs (using kill if necessary). Which version of relax are you using by the way? And which numpy version? The RelaxWarning message you see is either due to Python or numpy (specifically using newer versions). I have seen it many times before, and I try to avoid it in the code where possible. Strangely I have never seen this one before. The relax test suite tests the full automated dauvergne_protocol analysis, including multiple rounds of optimisation and convergence tests. And for each relax release I run the full test suite on Python version 2.5, 2.6, 2.7, 3.0, 3.1, 3.2, 3.3, and 3.4 (and now 3.5). Because the test suite has not replicated the problem you see, maybe it has something to do with numpy. Anyway, I look forward to seeing the traceback on that RelaxWarning, and maybe the output of 'relax -i'. If you'd like to attach files, then please create a bug report and attach the file to the report ( https://gna.org/bugs/?func=additem&group=relax ). Cheers, Edward > > > Sam > _______________________________________________ > relax (http://www.nmr-relax.com) > > This is the relax-users mailing list > relax-users@gna.org > > To unsubscribe from this list, get a password > reminder, or change your subscription options, > visit the list information page at > https://mail.gna.org/listinfo/relax-users _______________________________________________ relax (http://www.nmr-relax.com) This is the relax-users mailing list relax-users@gna.org To unsubscribe from this list, get a password reminder, or change your subscription options, visit the list information page at https://mail.gna.org/listinfo/relax-users
