Writing displacement to VTU with double precision output = true

[annajcrawford]

Computing system (please complete the following information):

• Machine name: Mahti and Archer

Issue Type
Is this issue:
'procedural': VTU files not writing properly

Error message or symptoms:
When bringing into Paraview this message is given:

A similar message is given when trying to work in Python.

Describe the context
I am modifying the io.f90 and wave2.f90 code to write out two additional variables to the STR files. I found that I need to set Double Precision Output = TRUE for these modifications. However, setting this to TRUE does not allow the VTU files to write properly. I am working on the modifications on Mahti but also tried simply setting Double Precision Output = TRUE on old successful sims on Archer to check that it wasn't an issue with the Mahti environment.

Expected behavior
Displacement be written to the VTU files correctly with Double Precision Output set to True.

Files
Nothing was written to the error log. Example files are in this Dropbox folder: https://www.dropbox.com/sh/h4wgd8v7d7ircb9/AADKwTZU1Gp6phPzg8PvJIuna?dl=0

[joeatodd]

If I run the test case with "Double Precision Output = True" I get reasonable output for the first timestep (running on local machine so no chance of making any actual progress through the simulation).

Can you show me what other modifications you've made to the code (perhaps by making your own branch and pushing it)?

[annajcrawford]

I've just invited you to my repository. I just pushed my files that currently comment out the lines to write additional variables to STR. The VTU issue still persists with these lines commented out and Double Precision Output set to 0. Thanks, Anna

…

________________________________ From: Joe Todd <[email protected]> Sent: January 5, 2021 12:44 PM To: joeatodd/HiDEM <[email protected]> Cc: Anna Crawford <[email protected]>; Author <[email protected]> Subject: {Disarmed} Re: [joeatodd/HiDEM] Writing displacement to VTU with double precision output = true (#5) If I run the test case with "Double Precision Output = True" I get reasonable output for the first timestep (running on local machine so no chance of making any actual progress through the simulation). Can you show me what other modifications you've made to the code (perhaps by making your own branch and pushing it)? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#5 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ALJBXE2S4OCGGIEGOWMAZW3SYMCRLANCNFSM4VU3DGZA>. [ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "#5 (comment)", "url": "#5 (comment)", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

[joeatodd]

This was a bug with the use of MPI_File_Set_View, should be fixed in commit ebae424