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

xmdf files generated by pyurdme examples faulty #153

Open
somathias opened this issue May 13, 2016 · 2 comments
Open

xmdf files generated by pyurdme examples faulty #153

somathias opened this issue May 13, 2016 · 2 comments
Assignees
Milestone

Comments

@somathias
Copy link

somathias commented May 13, 2016

When opening the xmdf files generated by the simple_diffusion example using paraview 4.4.0, the stored data values of the simulation are really small, ~ 10^-16 to 10^-21, ie. basically zero. Only the initial configuration seems to be stored with correct values.

I also ran the coral_reef and cylinder_demo examples, same problem.

@ahellander
Copy link
Owner

I think the numbers are “correct", but they are in concentration units (molecules/m^m3). If Paraview is not capable of rescaling the output in the visualization, we might have to apply some scaling ourselves.

/Andreas


Andreas Hellander
Associate Professor, Scientific Computing
Division of Scientific Computing
Department of Information Technology
Uppsala University

On May 13, 2016, at 1:51 PM, somathias <[email protected]mailto:[email protected]> wrote:

When opening the xmdf files generated by the simple_diffusion example using paraview 4.4, the stored data values of the simulation are really small, ~ 10^-16 to 10^-21, ie. basically zero. Only the initial configuration seems to be stored with correct values.

I also ran the coral_reef and cylinder_demo examples, same problem.


You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHubhttps://github.com//issues/153

@ahellander ahellander added this to the 1.2.0 milestone May 13, 2016
@ahellander ahellander self-assigned this May 13, 2016
@ahellander
Copy link
Owner

Verified. The problem is that the data range is too small to render in Paraview. Not sure if this should be treated as a bug in pyurdme or Paraview.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants