Trying to use flow renderer and/or issues with vdc create

I am trying to make a 3D flowline plot (actually a magnetic fieldline) out of three fields. I can’t see a way of using the flow renderer when I import variables as BOV since only one can be done per BOV. If I try a flow renderer, I cannot fill the other two fields, even if I have imported 3 BOVs. Can this be done?

To get around this, I tried to use vdc format instead, where I’ve done this before in the past. However, now, with Vapor3, I get an error when using vdccreate. Some librabry is missing. Here is the error:

brummell$ vdccreate -dimension 512x512x600 -vars3d Bx:By:Bz B.vdc
dyld[28622]: Library not loaded: ‘/usr/local/opt/xz/lib/liblzma.5.dylib’
Referenced from: ‘/Applications/vapor.app/Contents/lib/libtiff.6.dylib’
Reason: tried: ‘/usr/local/opt/xz/lib/liblzma.5.dylib’ (no such file), ‘/Applications/VAPOR.app/Contents/MacOS/liblzma.5.dylib’ (no such file)
Abort trap: 6

Any ideas on any of this?

Thanks in advance for any help!

Nic

Hi Nick, I’m going to file a bug report on this. Using VDC is a reasonable workaround for your raw data. We will discuss this today and get back to you.

1 Like

Hi Nick, we won’t be able to fix this for our next release but we should be able to have a fix in the next two weeks. I’ll get you an installer with the fix if you’d like. In the meantime, one option would be to convert the binary files into CF-Compliant NetCDF. That way you could include all of your field variables in files that could be directly read.

It would be great to have the fix when you have it, thanks! In the meantime, I’ll try the NetCDF route – that may well be just as easy, I’m just more used to the old way via vdccreate, raw2vdc etc!

1 Like

Just an update on this: My desktop is an Intel Mac and therefore I had downloaded Vapor 3.9. My laptop is an M1 Mac so I downloaded Vapor 3.10 there. On the latter, the vdccreate and raw2vdc worked. However, when I loaded a volume renderer, with variables set etc, I just got nothing (not even a white box). So it seems like there are two different issues on the two (Intel, Apple silicon) versions. Sorry!

Thank you for this information! It’s highly valuable to us and we are going to look into this for the next release.

Thanks again,
Scott