phoebe-project / phoebe2

PHOEBE - Eclipsing Binary Star Modeling Software
http://phoebe-project.org
GNU General Public License v3.0
76 stars 28 forks source link

Run_checks() always FAIL #916

Closed Randolph03 closed 1 day ago

Randolph03 commented 3 days ago

image I'm trying to run Nelder-Mead solver, but it's always stuck like this..., If I force it to run, it will simply become like this: messageImage_1719756527607

Addendum for when I check the constraint: image image

Randolph03 commented 3 days ago

for the dataset scaling, I think it's because I set the pblum into data-set scaled, but for the interchanging esinw & ecosw with the ecc & per0, I haven't figured out the reason yet

kecnry commented 2 days ago

Can you please include the full text of the checks report? They likely say which solver/solution they actually affect (these particular check failures will not affect calls to run_compute). If you want to adopt the proposed values for those parameters from that solution, you'll just need to manually flip the constraints first.

Randolph03 commented 1 day ago

Thank you! It indeed didn't affect the run_compute and I finally can got the solution from nm. I think the problem for my running previously is because I set the pblum into dataset-scaled and computed using phoebe01. I have changed it into fastcompute and pblum as component-coupled and set it so that the pblum@primary is also one of the fitted parameter and it works 👍

While I still didn't understand though why does it ask for me to flip my constraint (from ecc and per0 into esinw and ecosw), and when I did flip the constraint, it asked me to flip it back again (from esinw and ecosw inti ecc and per0), but aas long as it can run the compute, all well is well 😅

Once again, thank you for the response, much appreciated

kecnry commented 1 day ago

Each of the estimators propose values for different parameters, and when those don't match your current parameterization (the way you have the constraints set), they can only automatically translate the parameters to your parameterization if there is no ambiguity. If there is any ambiguity, then you would get this message when trying to adopt the results forcing you to decide which parameter(s) should instead by set (and which should remain fixed).

For the case of esinw and ecosw, there wouldn't technically be ambiguity, but PHOEBE isn't currently smart enough to realize that those two sets of equations are coupled together and therefore which sets e and which sets w ultimately won't matter.

Randolph03 commented 1 day ago

Ohhh I see, thank you very much for the explanation. I think this problem can be considered as solved.