-
Notifications
You must be signed in to change notification settings - Fork 31
Contact envelope reflection optimization #1020
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: feature-contacts
Are you sure you want to change the base?
Conversation
|
Ok, given the errors in 'contact' and 'reflection', I don't seem to understand how reflection actually is computed. reverting to draft |
|
Its definitely possible that that's the case and the tests are incorrect. Can you maybe expose the mesh at two times (perhaps even the same phase but one cycle apart) with and without irradiation enabled to show if this is indeed what is happening? |
…-reflection # Conflicts: # README.md # phoebe/__init__.py # pyproject.toml
|
rebasing on top of |
…eflection # Conflicts: # phoebe/__init__.py # phoebe/dynamics/nbody.py # phoebe/parameters/compute.py # pyproject.toml
|
is this intended to be a bugfix or no? I'll need to update the feature branch to get the jktebop fix yet if you want it rebased on that EDIT: |
remove abandoned run_tests script
…eflection # Conflicts: # phoebe/__init__.py # phoebe/dynamics/nbody.py # phoebe/parameters/compute.py # pyproject.toml
| # this will internally call save_as_standard mesh with the mesh | ||
| # of the ENTIRE contact envelope. | ||
| self._halves[0].update_position(*args, **kwargs) | ||
| self._halves[0].create_mesh(kwargs.get('ignore_effects')) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why is this change needed? This will be significantly more expensive than before, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think so? Calls to update_position will create the mesh if there no standard mesh available. Here I just isolated the mesh creation to a separate routine.



Currently,
libphoebe.mesh_radiosity_problem_nbody_convex()was called each iteration, leading to un-needed slowdown.I've overridden the appropriate properties of
Envelopeso this does not happen. In the current implementation of contact envelopes, I do not think we need to support any time/phase dependent quantities.