Unable to Render Variables in VAPOR 3.5 from VDC Files Created from Raw Data #2920
Comments
|
@robsopuh87 I think this is a problem with the size of your test data. 4x4x4 may be too small for VDC conversion. I'm going to write a new issue that summarizes your finding (#2926). I believe you can get around this problem with a larger grid. Check out this set of files that contain XYZ coordinates as text, and a 256^3 binary data set. Use the following commands and it should work.
|
|
Duplicate #2926 |
|
What is the resolution of the actual data that you want to convert? Unless they are "large" converting to NetCDF rather than VDC would be a better option. |
|
Hello,
Thank you for taking the time to provide a great resolution to my problem.
Let me explain something that I think I should have mentioned since the
beginning. In the ticket I opened on the github website, I included data
for a domain of size 4X4X4. However, this is not the actual data that I am
actually looking with. I created this data with the sole purpose of running
trials to try to catch what the problem was. The data that I am working
with is of the size 320X256X289 (it is a large data). However, every time I
was running the vdccreate and the raw2vdc commands to create a vdc file
with the actual data, I was getting the error: "short read file
y_coords.txt. I checked my text file of the y coordinates and indeed there
were 256 data points in it. I tried it multiple times and I continued
obtaining that error message on my Windows computer. I have tried
reproducing the same vdc file on a computer that uses Ubuntu to run a Linux
system but this does not work either.
I just tried running the commands you suggested with the 256f.bin data file
and all the text files that contain the coordinate data points and this
time it worked just fine on my version 3.4 on Windows. I have attached a
picture of the data that I obtained with the data from the file 256f.bin.
The resolution on the actual data, if I am understanding this correctly,
is: (delta_x, delta_y, delta_z) = (4.6875, 4.6875, 3.125) mm.
So if the 4X4X4 data is too small, what would be the reason that I can
create a vdc file in the computer that uses Ubuntu but I cannot
successfully do it in my Windows computer?
I have the text files with the actual data that contain the x, y, and z
coordinate data points. I can share them with you if you want to analyze
them. Let me know if it is OK for me to send them to you, please?
Technically, since the actual data is large, I should be able to create a
vdc file out of it with coordinate data points included.
…On Tue, Dec 7, 2021 at 3:56 PM clyne ***@***.***> wrote:
What is the resolution of the actual data that you want to convert? Unless
they are "large" converting to NetCDF rather than VDC would be a better
option.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2920 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ARA23WATASNZYBSMLG63CGDUPZ7IVANCNFSM5I77BIFQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
--
Robert Perez
M.S. Mechanical Engineering '22 | University of Houston
Di Yang's Research Group | Research Assistant
+1 (832) 731-5723 | ***@***.*** | ***@***.*** ***@***.***>*
|
|
@robsopuh87 Could you provide us with a data file on your 320x256x289 grid, along with any text files you're using to specify coordinates? Feel free to email us at vapor@ucar.edu if you need to keep the data private. |
|
Hello,
I just sent an email to ***@***.*** with the data files for x, y, and z
coordinates data points and files of variable values for a variable to be
rendered in VAPOR. The text file used to create the binary file of the
variable w is included. Both the binary and text files representing the
variable to be rendered are too large and only links to Google Drive were
included in the email.
Thank you for your help in this matter,
…On Fri, Dec 10, 2021 at 1:59 PM sgpearse ***@***.***> wrote:
@robsopuh87 <https://github.com/robsopuh87> Could you provide us with a
data file on your 320x256x289 grid, along with any text files you're using
to specify coordinates? Feel free to email us at ***@***.*** if you
need to keep the data private.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2920 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ARA23WFQJOMOPF27BBVRRKTUQJLZ3ANCNFSM5I77BIFQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
--
Robert Perez
M.S. Mechanical Engineering '22 | University of Houston
Di Yang's Research Group | Research Assistant
+1 (832) 731-5723 | ***@***.*** | ***@***.*** ***@***.***>*
|
|
Thanks Robert. I have the files. Can you provide the exact commands that demonstrate the bug with the files you've given? I have the commands for the 4x4x4 case, but not the one regarding your larger dataset. We need something like the following, but regarding your actual data: Thanks for your patience and for filing the bug report. |
|
Dear NCAR/VAPOR team,
I apologize for my late reply. Here are the two links that I have used in
the past:
vdccreate -vars3d var_w -dimension 320X256X289 -xcoords x_coords.txt
-ycoords y_coords.txt -zcoords z_coords.txt variable_w.vdc
raw2vdc -varname var_w variable_w.vdc variable_w_binary.bin
Thank you for your help,
…On Mon, Dec 13, 2021 at 6:38 PM sgpearse ***@***.***> wrote:
Thanks Robert. I have the files.
Can you provide the exact commands that demonstrate the bug with the files
you've given? I have the commands for the 4x4x4 case, but not the one
regarding your larger dataset. We need something like the following, but
regarding your actual data:
vdccreate -vars3d temp -dimension 4X4X4 temp.vdc
raw2vdc -varname temp temp.vdc temp_binary.bin
Thanks for your patience and for filing the bug report.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2920 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ARA23WB7VHHSEIGEI7TWRXDUQ2GY7ANCNFSM5I77BIFQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
--
Robert Perez
M.S. Mechanical Engineering '22 | University of Houston
Di Yang's Research Group | Research Assistant
+1 (832) 731-5723 | ***@***.*** | ***@***.*** ***@***.***>*
|
|
@robsopuh87 Robert, I'm able to reproduce the short read problem with the 3.5.0 installer, but not with our current weekly installer. I'm not sure what's happened to our file I/O between 3.5.0 and now, but could you try our weekly release and let us know if the problem persists? |
|
Dear VAPOR team, I have downloaded the weekly release as you have recommended me. The problem is resolved, and I no longer see the short read problem. Now, I am able to generate a vdc file that contains the coordinate data points of my domain. Thank you so much for all your help and time in this regard. |
|
Great, thanks for reporting this problem. I'll close the issue. Please don't hesitate to reach out again if you need help or find a bug. |
I recently updated to VAPOR 3.5 after used an older version, which I believed it was version 3.2, on my computer that runs on Windows 10 operating system. During I was using the older version of VAPOR, I was able to create vdc files from raw data using the vdccreate and raw2vdc utility functions. Recently I have been interested in specifying coordinate data points within the vdc file and since I was having a little difficulty in version 3.2, I though updating to version 3.5 would help me. But using version 3.5 has not helped and I have experience different issues. The data that I want to visualize in VAPOR is data that represents temperature. I have included, at the bottom of this description, the file that has the temperature data values named temp.txt and from which the binary data file temp_binary.bin has been created and I have also included in this ticket the files with coordinate data points named x_coords.txt, y_coords.txt, and z_coords.txt. I have tried creating a vdc file in two different ways. The first way, I only include the temperature data values in the vdc file. The second way, I include the coordinate data points and the temperature data values in the vdc file. When I only include the temperature data values using the vdccreate and the raw2vdc utilities, within the Command Prompt window, I proceed as follows:
vdccreate -vars3d temp -dimension 4X4X4 temp.vdc
raw2vdc -varname temp temp.vdc temp_binary.bin
The process seems to be fine and I do not get any errors on my Command Prompt Window. However, when I open the vdc file from VAPOR and try to render a volume, I do not get the correct output. I can only see a reddish color, and nothing makes sense. You can see what the output looks like in the picture named WrongData.png.
When I try to include the coordinate data points and the temperature data values in the vdc file using the vdccreate and raw2vdc utilities, within the Command Prompt window, I proceed as follows:
vdccreate -vars3d temp -xcoords x_coords.txt -ycoords y_coords.txt -zcoords z_coords.txt -dimension 4X4X4 temp.vdc
raw2vdc -varname temp temp.vdc temp_binary.bin
By including the coordinate data points, I also do not get any errors on the Command Prompt window. However, when I open the vdc file from VAPOR, it crushes, and the VAPOR window closes. I have deleted my VAPOR 3.5 version and download it again several times, but it has not helped, and I continue experiencing the same issue. A member of my group still has the version 3.4 and when we run the same commands with the same data files, we get the correct result when open the vdc file and create a volume render. The correct result of this data is shown in picture named ExpectedResults.JPG. This version of VAPOR 3.4 is installed in a Linux operating system. Before updating to version 3.5 on my Windows 10, I was not having problems rendering variables in VAPOR. I have even tried installing earlier version of VAPOR like 3.4, 3.3, and 3.2 but now none of them are working for me and I get the same failures. Thank you in advance for your help in this regard.
temp.txt
x_coords.txt
y_coords.txt
z_coords.txt
The text was updated successfully, but these errors were encountered: