Skip to content
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

Get an error when I try to change numerical parameters #1

Open
vholod opened this issue Dec 19, 2019 · 1 comment
Open

Get an error when I try to change numerical parameters #1

vholod opened this issue Dec 19, 2019 · 1 comment
Labels
bug Something isn't working

Comments

@vholod
Copy link

vholod commented Dec 19, 2019

Hi Dear aviadlevis,
Thank you for sharing this great work.
I have a problem to render images of my own data. If I just use the default numerical parameters as it is used the notebook example Radiance Rendering [Single Image], I get bad results.
So I try to play with the numerical parameters in order to improve the results.
I try to set the following:
numerical_params = shdom.NumericalParameters(num_mu_bins=16,num_phi_bins=32)
On the data of the Radiance Rendering [Single Image] notebook it works. but on my data, it doesn't.
I get the following error:
"builtins.ValueError: failed to create intent(cache|hide)|optional array-- must have defined dimensions but got (-40504832,)"

it happens when I run the command
rte_solver.solve(maxiter=100)
and the failure occurs when it tries to execute the function
init_solution (inside rte_solver.py).
`
Are you familiar with this kind of error?
Do you need my data to debug it?

Many thanks,
Vadim

@JRLoveridge
Copy link
Collaborator

Hi Vadim,

I have encountered a similar error (just recently) when pushing the accuracy for a small domain but I haven't uncovered it yet. The parameter (nphi0max) that allocates the maximum size of some arrays must have encountered some issue (?) to give a nonsense negative number similar to you describe. Is there a detailed traceback that describes exactly where in the code this failed or is this the only information?

I am guessing that your domain is very large to give a similar error at that accuracy. Could you tell me about the number of grid points you are using?
It would also be helpful if you post the images at lower accuracy that you where unhappy with to see if there are obvious artifacts that we can give advice on removing.

Best,
Jesse

@JRLoveridge JRLoveridge added the bug Something isn't working label Dec 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants