#Flexihub node limit reached code#
For mxTryHard(), the default is to consider any nonzero status code "unacceptable". It says the solution is imperfect, meaning that it did not have an "acceptable" status code. The ouptut for the ones where I would expect 1 is:Ĭomputing Hessian and/or standard errors and/or confidence intervals from imperfect sol A nonzero status code, by itself, only raises a warning and not an error. The 0 errors just means that none of the attempts (calls to mxRun()) raised errors. It does say 0 errors, so I'm not sure if we would expect status code 0 or 1 from this? Otherwise the only thing I can think to do is use my error files from job submission and use bash to grep out where these are, but something built into OpenMx might be useful. For my purpose this could just be a 0 or 1 output, but it's possible there might be something more widely useful. So increasing the number of tries probably is not ideal, but just knowing which ones give me solution found and which ones give me retry limit reached would be useful, so I know which outputs are ok and which are based on imperfect soutions. With just the normal mxTryHard some of them do not finish within 100 hours on a cluster. I have not used extra tries as the model would probably take a very long time to run for some of my 42 jobs. The data is binary so I am using a liability threshold model and also trying to estimate CIs, so I think for some models it might just be that the model is a little harder to estimate. So I am just using mxTryHard() alone within a for loop over 100 models (although I run this parallelised 42 times as I have 4,200 models to run).
0 kommentar(er)
