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
I encountered the following error running the AMReX tutorial HeatEquation_EX1_C and using Amrvis to visualize the results. The error occurs in both DIM = 2 and 3 dimensions, but I will cite the DIM = 3 case here.
Plot files were produced using
./main3d.gnu.ex inputs_3d
One plot file was brought into amrvis
amrvis3d plt00000 &
Invoking the menu item Help --> Info... yields the following file information:
plt00000
HyperCLaw-V1.1
time: 0
levels: 1
prob domain:
level 0: ((0,0,0) (127,127,127) (0,0,0))
refratios:
probsize: 2 2 2
prob lo: -1 -1 -1
prob hi: 1 1 1
Note that the physical problem domain is [-1, 1] x [-1, 1] x [-1, 1].
To look at a two dimensional slice of this data, I ran the batch command,
amrvis3d -newplt -zslice 80 plt00000
and brought this slice into amrvis via
amrvis3d -fab plt00000.phi.zslice.80.Level_0.fab
The information on this file reads
plt00000.phi.zslice.80.Level_0.fab
FromFAB
time: 0
levels: 1
prob domain:
level 0: ((0,0,80) (127,127,80) (0,0,0))
refratios:
probsize: 1 1 1
prob lo: 0 0 0
prob hi: 1 1 1
The domain has been erroneously rescaled to [0, 1] x [0, 1] x [0, 1].
My original intent was to bring this Fab slice into amrvis2d so that I may extract line plots (which doesn't seem to be possible within amrvis3d). The command
amrvis3d -fab plt00000.phi.zslice.80.Level_0.fab
happily worked, but with the same rescaling error as above.
Previously I had encountered the same rescaling problems using amrvis2d to batch produce slices, which in that case were data along a line.
The text was updated successfully, but these errors were encountered:
This is because a Fab has no notion of a domain size or delta x. It is just data on a regular grid. amrvis has to draw something, so it makes something up for those values.
On Aug 16, 2019, at 2:58 PM, Marc Day ***@***.***> wrote:
This is because a Fab has no notion of a domain size or delta x. It is just data on a regular grid. amrvis has to draw something, so it makes something up for those values.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#4?email_source=notifications&email_token=AM5NDEKMFGHKHWZIZSUFJXLQE4BEVA5CNFSM4IMLV2XKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4PR4CA#issuecomment-522133000>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AM5NDEIOLX6HNFUPZ7IB5XDQE4BEVANCNFSM4IMLV2XA>.
I encountered the following error running the AMReX tutorial HeatEquation_EX1_C and using Amrvis to visualize the results. The error occurs in both DIM = 2 and 3 dimensions, but I will cite the DIM = 3 case here.
Plot files were produced using
./main3d.gnu.ex inputs_3d
One plot file was brought into amrvis
amrvis3d plt00000 &
Invoking the menu item Help --> Info... yields the following file information:
plt00000
HyperCLaw-V1.1
time: 0
levels: 1
prob domain:
level 0: ((0,0,0) (127,127,127) (0,0,0))
refratios:
probsize: 2 2 2
prob lo: -1 -1 -1
prob hi: 1 1 1
Note that the physical problem domain is [-1, 1] x [-1, 1] x [-1, 1].
To look at a two dimensional slice of this data, I ran the batch command,
amrvis3d -newplt -zslice 80 plt00000
and brought this slice into amrvis via
amrvis3d -fab plt00000.phi.zslice.80.Level_0.fab
The information on this file reads
plt00000.phi.zslice.80.Level_0.fab
FromFAB
time: 0
levels: 1
prob domain:
level 0: ((0,0,80) (127,127,80) (0,0,0))
refratios:
probsize: 1 1 1
prob lo: 0 0 0
prob hi: 1 1 1
The domain has been erroneously rescaled to [0, 1] x [0, 1] x [0, 1].
My original intent was to bring this Fab slice into amrvis2d so that I may extract line plots (which doesn't seem to be possible within amrvis3d). The command
amrvis3d -fab plt00000.phi.zslice.80.Level_0.fab
happily worked, but with the same rescaling error as above.
Previously I had encountered the same rescaling problems using amrvis2d to batch produce slices, which in that case were data along a line.
The text was updated successfully, but these errors were encountered: