# Display of FVCOM data broken in recent nightlies

**URL:** https://discourse.paraview.org/t/display-of-fvcom-data-broken-in-recent-nightlies/1896
**Category:** Development
**Created:** [May 21, 2019, 8:18pm UTC](https://discourse.paraview.org/t/display-of-fvcom-data-broken-in-recent-nightlies/1896 "2019-05-21T20:18:53Z")
**Posts on this page:** 16
**Page:** 1

<div class="post-metadata">

### Author: ![swaldman](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/s/f19dbf/32.png) [@swaldman](https://discourse.paraview.org/u/swaldman)
#### Post date: [May 21, 2019, 8:18pm UTC](https://discourse.paraview.org/t/display-of-fvcom-data-broken-in-recent-nightlies/1896/1 "2019-05-21T20:18:53Z")

</div>

Hi all,  
My apologies in advance for a not-ideal bug report. Everything below is on Windows, but I don’t have the ability to run the linux version, so I can’t tell you whether it is Windows-specific.

In 5.6.0, I can open FVCOM output files (which are netCDF, using the “VisItNetCDFFVCOM\_MTSDReader” reader). There’s the known problem in 5.6.0 in Windows that it won’t read files of \>2Gb, but otherwise it works, and some beautiful plots are possible.

In recent nightly builds (I’ve tested 1554 and 1598), the large file problem is fixed, but reading FVCOM files seems to be broken. I can open them happily, and see the available fields populated in the Properties pane, but no matter what I select and Apply I never see anything rendered, and the toolbars that control color maps, rendering type, etc., stay greyed out. There’s nothing relevant in the Output Messages.

Rendering is not broken for all data - the example files that ship with Paraview still display - but I can’t get anything from FVCOM to show.

Here’s a relatively small (47Mb) example file that works on 5.6.0 but not in recent nightlies:

> **[casename\_0001\_modified\_z.nc](https://www.dropbox.com/s/8otkg1bxwprm0me/casename_0001_modified_z.nc?dl=0)**
>
> Shared with Dropbox

Beyond this, please let me know if I can usefully provide any other info, or if you’d like me to file a bug report on gitlab.

Simon.

---

<div class="post-metadata">

### Author: ![swaldman](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/s/f19dbf/32.png) [@swaldman](https://discourse.paraview.org/u/swaldman)
#### Post date: [May 22, 2019, 4:27pm UTC](https://discourse.paraview.org/t/display-of-fvcom-data-broken-in-recent-nightlies/1896/2 "2019-05-22T16:27:48Z")

</div>

I can now offer an example data file that works in 5.6.0 but not in 1598.  
It’s 47Mb, and is at [https://www.dropbox.com/s/8otkg1bxwprm0me/casename\_0001\_modified\_z.nc?dl=0](https://www.dropbox.com/s/8otkg1bxwprm0me/casename_0001_modified_z.nc?dl=0)

---

<div class="post-metadata">

### Author: ![cory.quammen](https://discourse.paraview.org/user_avatar/discourse.paraview.org/cory.quammen/32/11193_2.png) [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [June 19, 2019, 3:53pm UTC](https://discourse.paraview.org/t/display-of-fvcom-data-broken-in-recent-nightlies/1896/3 "2019-06-19T15:53:13Z")

</div>

We recently updated the NetCDF library. Could you try the most recent nightly and report if you see the problem?

I just tried on macOS from a recent nightly and was able to load the data.

---

<div class="post-metadata">

### Author: ![swaldman](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/s/f19dbf/32.png) [@swaldman](https://discourse.paraview.org/u/swaldman)
#### Post date: [June 19, 2019, 5:59pm UTC](https://discourse.paraview.org/t/display-of-fvcom-data-broken-in-recent-nightlies/1896/4 "2019-06-19T17:59:03Z")

</div>

Same problem with 1703, I’m afraid. Maybe this is a Windows-specific issue?

That suggests to me that it might be a regression related to [https://gitlab.kitware.com/paraview/paraview/issues/18661](https://gitlab.kitware.com/paraview/paraview/issues/18661), but I can’t be sure as I wasn’t running nightlies before that fix went in. I’m sorry for what may have been inadequate testing before I said that that fix had helped!

- In versions 5.6.0 and 5.6.1, I can open and plot from FVCOM files of \<2Gb, but anything over 2Gb fails.
- In nightly builds 1554, 1598, and 1703 (those are the ones I’ve tested) I can open FVCOM files of any size - which is the fix from the issue above - but none of them will render.

I note that 5.6.1 came after nightly 1598, but that may not signify anything, depending on how versions are managed and what makes it in to numbered releases.

Just in case it matters I’m using the non-MPI version of the Windows download. If I should try the MPI version, let me know.

Thanks for looking into this!

---

<div class="post-metadata">

### Author: ![liuqi18810676518](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/l/c37758/32.png) [@liuqi18810676518](https://discourse.paraview.org/u/liuqi18810676518)
#### Post date: [September 27, 2020, 3:30am UTC](https://discourse.paraview.org/t/display-of-fvcom-data-broken-in-recent-nightlies/1896/5 "2020-09-27T03:30:46Z")

</div>

Hey friend, I encountered the same problem. I used 5.8.0 and the latest version to open FVCOM output files, but neither of them work. I tried both on Windows and Mac. I want to know if you solved the problem? Thank you!

---

<div class="post-metadata">

### Author: ![sitepan](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/s/e19b73/32.png) [@sitepan](https://discourse.paraview.org/u/sitepan)
#### Post date: [September 14, 2021, 3:16am UTC](https://discourse.paraview.org/t/display-of-fvcom-data-broken-in-recent-nightlies/1896/6 "2021-09-14T03:16:05Z")

</div>

I have the same problem when using the paraview5.9.1, but it’s normal in the paraview5.6.2

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [September 14, 2021, 10:37am UTC](https://discourse.paraview.org/t/display-of-fvcom-data-broken-in-recent-nightlies/1896/7 "2021-09-14T10:37:48Z")

</div>

Please share some data

---

<div class="post-metadata">

### Author: ![sitepan](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/s/e19b73/32.png) [@sitepan](https://discourse.paraview.org/u/sitepan)
#### Post date: [September 15, 2021, 2:54am UTC](https://discourse.paraview.org/t/display-of-fvcom-data-broken-in-recent-nightlies/1896/8 "2021-09-15T02:54:15Z")

</div>

I can load and render this data using 5.6.2 under Windows. In the 5.9.0 ,5.8.0 or 5.7.0 ,I can only load this data, but the paraview can not render it while I apply it.

> **[case.nc](https://onedrive.live.com/redir?resid=3C875A5957D066A%21193&authkey=%21AGf2QEqEBERRdu8&e=G44DKT)**
>
> NC File

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [September 15, 2021, 7:36am UTC](https://discourse.paraview.org/t/display-of-fvcom-data-broken-in-recent-nightlies/1896/9 "2021-09-15T07:36:40Z")

</div>

I seem to reproduce, next step would be to open an issue on our gitlab  
[https://gitlab.kitware.com/paraview/paraview/issues/](https://gitlab.kitware.com/paraview/paraview/issues/)

---

<div class="post-metadata">

### Author: ![yoga](https://discourse.paraview.org/user_avatar/discourse.paraview.org/yoga/32/10303_2.png) [@yoga](https://discourse.paraview.org/u/yoga)
#### Post date: [October 30, 2022, 2:59pm UTC](https://discourse.paraview.org/t/display-of-fvcom-data-broken-in-recent-nightlies/1896/10 "2022-10-30T14:59:32Z")

</div>

Hi, Mathieu,

The rendering problem for VisItNetCDFFVCOM\_MTSDReader seems still remains for the latest version. Is it possible for a quick fix?  
One more thing to bother you, I tried client/server mode to post-processing fvcom data, but when I connected to supercomputer with paraview version 5.6.2-foss-2019b-Python-3.7.4-mpi, I cannot find the VisItNetCDFFVCOM\_MTSDReader. However, when disconnected from the server, the reader is available. How could I solve this problem?  
,

Thanks for your answer.

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [October 31, 2022, 1:20am UTC](https://discourse.paraview.org/t/display-of-fvcom-data-broken-in-recent-nightlies/1896/11 "2022-10-31T01:20:33Z")

</div>

Hi @yoga

> [@mwestphal](#):
>
> next step would be to open an issue on our gitlab  
> [https://gitlab.kitware.com/paraview/paraview/issues/](https://gitlab.kitware.com/paraview/paraview/issues/)

Best,

---

<div class="post-metadata">

### Author: ![yoga](https://discourse.paraview.org/user_avatar/discourse.paraview.org/yoga/32/10303_2.png) [@yoga](https://discourse.paraview.org/u/yoga)
#### Post date: [October 31, 2022, 9:32am UTC](https://discourse.paraview.org/t/display-of-fvcom-data-broken-in-recent-nightlies/1896/12 "2022-10-31T09:32:05Z")

</div>

Hi, Mathieu,

Thanks for quick reply.

The rendering problem needs to be solved first (there is already an open issue posted in the gitlab, about one year ago). All versions after 5.6.2 have this problem. Here is a dilemma. VisItNetCDFFVCOM\_MTSDReader is only usable for version 5.6.2 or earlier, but for files of \<2Gb. We normally have files \>2Gb. Later versions can load files \>2Gb, but cannot render. So basically, we cannot use this Reader, which is a pity.

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [October 31, 2022, 9:33am UTC](https://discourse.paraview.org/t/display-of-fvcom-data-broken-in-recent-nightlies/1896/13 "2022-10-31T09:33:30Z")

</div>

Hi @yoga

Do you have a link to this issue ?

---

<div class="post-metadata">

### Author: ![yoga](https://discourse.paraview.org/user_avatar/discourse.paraview.org/yoga/32/10303_2.png) [@yoga](https://discourse.paraview.org/u/yoga)
#### Post date: [October 31, 2022, 10:11am UTC](https://discourse.paraview.org/t/display-of-fvcom-data-broken-in-recent-nightlies/1896/14 "2022-10-31T10:11:05Z")

</div>

Hi, Mathieu,

See the link:

[https://gitlab.kitware.com/paraview/paraview/-/issues/21030](https://gitlab.kitware.com/paraview/paraview/-/issues/21030)

---

<div class="post-metadata">

### Author: ![Sebin\_John](https://discourse.paraview.org/user_avatar/discourse.paraview.org/sebin_john/32/11881_2.png) [@Sebin\_John](https://discourse.paraview.org/u/Sebin_John)
#### Post date: [June 25, 2023, 2:53am UTC](https://discourse.paraview.org/t/display-of-fvcom-data-broken-in-recent-nightlies/1896/15 "2023-06-25T02:53:57Z")

</div>

Hi mathieu,  
Is this issues was solved . I am also facing same problem in my machine (mac) with paraview5.11.1.

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [June 28, 2023, 7:36am UTC](https://discourse.paraview.org/t/display-of-fvcom-data-broken-in-recent-nightlies/1896/16 "2023-06-28T07:36:54Z")

</div>

This issue has not been solved yet.
