You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Integrator is selected according to the loaded scene parameters in the scene.
CRQ
The integrator should be selected according to the selected scene parameters by the user. Consequently, one can avoid using discontinuity handling integrators if the selected parameters do not introduce discontinuities. Currently this is not the case.
See also: david.hahn: Is this not a question of whether the user has actually selected such a parameter for optimization? Could this selection change after file loading?
Feb 21, 2023 4:02 PM
You: This is a good CRQ
Feb 21, 2023 8:06 PM • Edit • Delete
You: However, the main difficulty mitsuba does not seem to allow changing the integrator after loading it :-(
Feb 21, 2023 8:07 PM • Edit • Delete
david.hahn: hm ok, now I'm a bit confused - doesn't then every scene have some potential for discontinuity? anyway if we end up always using path-replay backprop, that's fine too
Feb 23, 2023 9:34 AM
You: >> doesn't then every scene have some potential for discontinuity?
True.
I kinda build a workaround:
First the scene is loaded temporarily to control what type of scene parameters it contains.
Depending on those parameters, an integrator gets suggested.
Eventually, the model really loads the scene and uses that suggested integrator.
Feb 23, 2023 9:50 AM • Edit • Delete
You: Unfortunately its quite messy, but currently that's how mitsuba work--it also caused headache for scene resolution. The scene is reloaded everytime when user loads images, since the scene resolution is modified according to the loaded images --> messy :-(
The text was updated successfully, but these errors were encountered:
Current state
Integrator is selected according to the loaded scene parameters in the scene.
CRQ
The integrator should be selected according to the selected scene parameters by the user. Consequently, one can avoid using discontinuity handling integrators if the selected parameters do not introduce discontinuities. Currently this is not the case.
See also:
david.hahn: Is this not a question of whether the user has actually selected such a parameter for optimization? Could this selection change after file loading?
Feb 21, 2023 4:02 PM
You: This is a good CRQ
Feb 21, 2023 8:06 PM • Edit • Delete
You: However, the main difficulty mitsuba does not seem to allow changing the integrator after loading it :-(
Feb 21, 2023 8:07 PM • Edit • Delete
david.hahn: hm ok, now I'm a bit confused - doesn't then every scene have some potential for discontinuity? anyway if we end up always using path-replay backprop, that's fine too
Feb 23, 2023 9:34 AM
You: >> doesn't then every scene have some potential for discontinuity?
True.
I kinda build a workaround:
First the scene is loaded temporarily to control what type of scene parameters it contains.
Depending on those parameters, an integrator gets suggested.
Eventually, the model really loads the scene and uses that suggested integrator.
Feb 23, 2023 9:50 AM • Edit • Delete
You: Unfortunately its quite messy, but currently that's how mitsuba work--it also caused headache for scene resolution. The scene is reloaded everytime when user loads images, since the scene resolution is modified according to the loaded images --> messy :-(
The text was updated successfully, but these errors were encountered: