Replies: 1 comment 1 reply
-
Hi Jeppe - this has been on the wishlist for a while, but would require a significant rewrite of some code to do in one single step and I don't see that being added anytime in the near future unless someone wants to take a fairly big project on. But this was a fun challenge to get some examples with what currently is supported. If you do NOT want to see eclipsesYou can tell one of the stars to skip meshing (emit no light, do NOT eclipse, but still have mass) with Multiple calls to
Putting together this example actually exposed an interesting behavior here that I'm not sure if it should be considered a bug or just a consequence of the parameters (I'd be curious to hear your, and others', opinion). Since This makes sense with what you'd expect. In a real system, you could do this by using passband-coupling with both components on, manually compute the two passbands, and then set them after decoupling:
In theory, I would have also expected the following to work for a single call to
If you DO want to see eclipsesNow things are really inconvenient, and the only current way to get what you want is by populated and exposing the mesh at each time and integrating over a single star to build your own light curve.
|
Beta Was this translation helpful? Give feedback.
-
Hi everyone!
I have a niche case where I would like to see the light curve split into two. Basically, the contribution of the primary and the secondary, as two separate outputs.
Is that something that is doable with the way PHOEBE is designed? And could you point me to either a ressource, or the code-snippet that handles the "output" light curve?
All the best,
Jeppe
Beta Was this translation helpful? Give feedback.
All reactions