Replies: 4 comments 19 replies
-
|
These again are probably intermediate warnings. As long as the system passes b.run_checks and the original forward model runs successfully, it shouldn't be an issue. How long does run_compute take? Contact binaries can be quite expensive, and each iteration in Nelder-Mead will require several calls to run_compute, so I'm not surprised if it takes quite a while. It's probably well worth the effort to try to optimize your forward model as much as possible first. This tutorial from the latest workshop covers some of the things you might want to try. |
Beta Was this translation helpful? Give feedback.
-
|
So, b.run_checks() give status = PASS, and the first run_compute takes about 9 seconds to run, so I assume that means all the errors and warnings after entering the system parameters don't matter. Then I try adding in the optimiser and when it gets to run_solver it goes really slowly and eventually seems to stop. I will have a look at the tutorial you mentioned and see if that helps. Thanks again! :) |
Beta Was this translation helpful? Give feedback.
-
|
Ok, great! I think that should help you speed things up a bit. By seems to stop do you mean it completes before you expected or that the progress bar gets stuck and it stalls entirely? |
Beta Was this translation helpful? Give feedback.
-
|
The progress bar gets stuck at the 18th iteration and it seems to stall entirely. I have left it for maybe 10minutes or so and it is still at iteration 18 |
Beta Was this translation helpful? Give feedback.
-
|
Ok... then I don't think speeding it up will likely fix that (although still will be useful to do once it is working). My guess is that the optimizer is wandering into an area of the parameter space where building the mesh is hanging. Can you enable a debugging logger and send me the output? Immediately before run_solver, add If you can also send me a copy of the bundle immediately before calling run_solver, that would be easiest for me to try to reproduce. If you don't want to attach it publicly here, you can send it to me by email. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Hi Kyle, here are the files, hope it works this time! Safe travels! |
Beta Was this translation helpful? Give feedback.
-
|
Hi Kyle,
I have now added in the code for the debugging logger, and although it made a file, it didn't write anything to it. Please find attached snapshots of my file so far. I have tried to keep it simple by commenting out some of the parameters I entered that I don't think are so important to see if that helped. And so far I only have one of my 3 passbands in the file. I hope the snapshots are enough for you to be able to see what I am trying to do. If you need anything else, please let me know.
Thanks again,
Kathryn
…________________________________
From: Kyle Conroy ***@***.***>
Sent: 28 July 2021 19:55
To: phoebe-project/phoebe2 ***@***.***>
Cc: kathmcp ***@***.***>; Author ***@***.***>
Subject: Re: [phoebe-project/phoebe2] Nelder-Mead optimizer (#508)
Ok... then I don't think speeding it up will likely fix that (although still will be useful to do once it is working). My guess is that the optimizer is wandering into an area of the parameter space where building the mesh is hanging.
Can you enable a debugging logger and send me the output? Immediately before run_solver, add phoebe.logger(flevel='DEBUG', filename='debug.log') (and remove any previous logger statements). Then just run the script, wait for it to stall again, and send me the last 50 or so lines of that log file.
If you can also send me a copy of the bundle immediately before calling run_solver, that would be easiest for me to try to reproduce. If you don't want to attach it publicly here, you can send it to me by email.
Thanks!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fphoebe-project%2Fphoebe2%2Fdiscussions%2F508%23discussioncomment-1084089&data=04%7C01%7C%7Cc793396aabbc44c91d7608d95201b5e2%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637630989561188247%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=wbMYop6DVlfLadKlocmmcoQX6W3EdnaB6OuuP6iesbs%3D&reserved=0>, or unsubscribe<https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FATNTCQIHX6QWV6VZUARKE4DT2BOEVANCNFSM5BEWTPEA&data=04%7C01%7C%7Cc793396aabbc44c91d7608d95201b5e2%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637630989561188247%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=mKJkPTRZglXIJZtuPWaI682BNfzdMVfKuw0PB6T%2F1uA%3D&reserved=0>.
|
Beta Was this translation helpful? Give feedback.
-
|
Neither of the files attached correctly (that seems to happen if attaching as a reply by email to the discussion). Can you either try attaching them from GitHub directly and/or just email them to me. I'm traveling over the next few days, but will try to look into it as soon as I can. |
Beta Was this translation helpful? Give feedback.
-
|
Here is the csv file with the observations in it, if that's of any help.
Thanks,
Kathryn
…________________________________
From: Kyle Conroy ***@***.***>
Sent: 28 July 2021 19:55
To: phoebe-project/phoebe2 ***@***.***>
Cc: kathmcp ***@***.***>; Author ***@***.***>
Subject: Re: [phoebe-project/phoebe2] Nelder-Mead optimizer (#508)
Ok... then I don't think speeding it up will likely fix that (although still will be useful to do once it is working). My guess is that the optimizer is wandering into an area of the parameter space where building the mesh is hanging.
Can you enable a debugging logger and send me the output? Immediately before run_solver, add phoebe.logger(flevel='DEBUG', filename='debug.log') (and remove any previous logger statements). Then just run the script, wait for it to stall again, and send me the last 50 or so lines of that log file.
If you can also send me a copy of the bundle immediately before calling run_solver, that would be easiest for me to try to reproduce. If you don't want to attach it publicly here, you can send it to me by email.
Thanks!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fphoebe-project%2Fphoebe2%2Fdiscussions%2F508%23discussioncomment-1084089&data=04%7C01%7C%7Cc793396aabbc44c91d7608d95201b5e2%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637630989561188247%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=wbMYop6DVlfLadKlocmmcoQX6W3EdnaB6OuuP6iesbs%3D&reserved=0>, or unsubscribe<https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FATNTCQIHX6QWV6VZUARKE4DT2BOEVANCNFSM5BEWTPEA&data=04%7C01%7C%7Cc793396aabbc44c91d7608d95201b5e2%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637630989561188247%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=mKJkPTRZglXIJZtuPWaI682BNfzdMVfKuw0PB6T%2F1uA%3D&reserved=0>.
|
Beta Was this translation helpful? Give feedback.
-
|
Hi Kyle, sorry, I thought I had attached the files in here last night, but they are not here, so here they are again, along with an xls file of the observations if you need it. thanks!
|
Beta Was this translation helpful? Give feedback.
-
|
Hi Kyle, I have uninstalled and reinstalled phoebe, but I can't seem to get it to go back to v2.3.49, so am persevering with v2.3.50. When I run the file with the parameters I sent you before (q=0.15, sma=1.85, requiv@primary=1.05), it fails 2 checks at run_checks, and the warnings tell me requiv needs to be between 1.27 and 1.67. I then change requiv to 1.3, and have tried various combinations of sma and q, but I keep getting the following errors and warnings. Do I just need to keep adjusting these parameters until something works? WARNING constraints ['pot@contact_envelope@envelope@constraint'] failed to run. Address errors and try again. Call run_failed_constraints to see the tracebacks. If not addressed, this warning will continue to be raised and will throw an error at run_compute. |
Beta Was this translation helpful? Give feedback.
-
|
Hi again Kyle, I am thinking that if it ran on your computer, but doesn't run on mine, I might try buying a new laptop (we would need a new one soon anyway). What specifications would be needed for PHOEBE? It will be another Windows system, as I am not familiar with Mac and don't have time to learn. I would be grateful for any advice :) |
Beta Was this translation helpful? Give feedback.
-
|
Hi Kyle, I have bought a new computer now, and reinstalled everything (WSL2, Ubuntu and Miniconda3, and then PHOEBE) following the instructions for Conda Environments from here http://phoebe-project.org/install/latest/linux/auto. Everything seems to work ok, but the file is still not running. I have tried version 2.3.50 and 2.3.49, but neither works. As far as I can see I haven't changed any inputs, so I have no idea why run_compute() ran before and isn't running now. I am still getting the errors above, and also this one below now. When I check what value of asini it has calculated after my initial input parameters, it still has 3.5 (from default values I think). Then later after some more inputs (and after run_compute(), it says asini failed to run (the second error noted below). There are numerous other errors too. If I can send you anything to help, please feel free to ask. Thanks again for any help! ERROR Constraint 'asini@binary@orbit@constraint' raised the following error while attempting to solve for 'asini@binary@orbit@component'. Consider flipping the constraint or changing the value of one of ['sma@binary@orbit@component', 'incl@binary@orbit@component', 'asini@binary@orbit@component'] until the constraint succeeds. Original error: cannot convert object with physical_type=length to solar units WARNING constraints ['asini@binary@orbit@constraint'] failed to run. Address errors and try again. Call run_failed_constraints to see the tracebacks. If not addressed, this warning will continue to be raised and will throw an error at run_compute. |
Beta Was this translation helpful? Give feedback.
-
|
The issue you're seeing now is still related to the bugfix you posted (#509) - the underlying cause seems to have been an update to astropy which broke the way phoebe handled parsing and converting units in constraints. I am testing a fix for that now and will try to release an updated 2.3.51 which should get that working for you. See that issue or keep a lookout for the release for more details. Hopefully the new machine with more memory will help with the stalling issues you had once that is out! |
Beta Was this translation helpful? Give feedback.
-
|
Ok fantastic, thank you! |
Beta Was this translation helpful? Give feedback.
-
Hi Kyle,
I am now trying to run the Nelder-Mead optimizer, but it seems to be running very, very slowly. It is taking about 20s per iteration, and then after 18 iterations it seems to have just stopped. I removed the orb and mesh datasets, so it's only running one light curve, but this didn't seem to help. I also tried using fast compute with ellc, but it doesn't work for contact binaries. I am trying to just vary the mass ratio, initially.
When I first enter the parameters for my binary, I get the following errors and warnings (although it does run_compute later)
Wed, 28 Jul 2021 16:30 BUNDLE ERROR Constraint 'pot@contact_envelope@envelope@constraint' raised the following error while attempting to solve for 'pot@contact_envelope@envelope@component'. Consider flipping the constraint or changing the value of one of ['requiv@primary@star@component', 'q@binary@orbit@component', 'sma@binary@orbit@component', 'pot@contact_envelope@envelope@component'] until the constraint succeeds. Original error: roche_contact_Omega_at_partial_vol::Volume is outside bounds.
Wed, 28 Jul 2021 16:30 BUNDLE ERROR Constraint 'requiv@secondary@star@constraint' raised the following error while attempting to solve for 'requiv@secondary@star@component'. Consider flipping the constraint or changing the value of one of ['pot@contact_envelope@envelope@component', 'q@binary@orbit@component', 'sma@binary@orbit@component', 'requiv@secondary@star@component'] until the constraint succeeds. Original error: potential > L1 critical value
Wed, 28 Jul 2021 16:30 BUNDLE ERROR Constraint 'fillout_factor@contact_envelope@envelope@constraint' raised the following error while setting the value of 'fillout_factor@contact_envelope@envelope@component'. Original error: value of fillout_factor=-13.410026693369053 not within limits of [<Quantity 0.>, <Quantity 1.>]
Wed, 28 Jul 2021 16:30 BUNDLE WARNING constraints ['pot@contact_envelope@envelope@constraint'] failed to run. Address errors and try again. Call run_failed_constraints to see the tracebacks. If not addressed, this warning will continue to be raised and will throw an error at run_compute.
Wed, 28 Jul 2021 16:30 BUNDLE WARNING primary is underflowing at L1 and not a contact system (requiv=1.5, requiv_min=1.8346231503528594, requiv_max=1.9639267680718653) If not addressed, this warning will continue to be raised and will throw an error at run_compute.
Wed, 28 Jul 2021 16:30 BUNDLE WARNING secondary is overflowing at L2/L3 (requiv=1.4999999999999996, requiv_min=1.2725418568681297, requiv_max=0.9342870720587503) If not addressed, this warning will continue to be raised and will throw an error at run_compute.
Are these errors and warnings contributing to the problems with the optimizer?
Beta Was this translation helpful? Give feedback.
All reactions