On a development branch of PyFR I am exporting a large mixed element mesh composed of prisms and tets, but the VTU appears to contain only the near wall prisms. Is this an issue or am I missing some setting?
pyfr export volume -p double mesh.pyfrm sol.pyfrs sol.vtu
That should work. Do you have a reproducer? We rewrote quite a bit of that code recently when we added a clean-to-grid path.
Regards, Freddie.
I should have said that perhaps the SHA I am working with is not the most recent is the one when @tobyflynn fixed the gradients in Ascent plugin. I just want to verify that mixed element export worked at this point?
I noticed there was a lot of development since then and the meshes I used back in March are no longer working for export on the latest develop branch commit, but if there’s an easy way to convert those meshes that would be great. I have solution files I need to re-export for analysis and I cannot now rerun from scratch.
I believe it was working, yes. If you look at pyfr upgrade you’ll see how to upgrade files from the old format to the new format. Note if your mesh/solution is from an intermediate time then you may need to hack this a little (since it will be half way to v2 already). Then you can run through the current tooling.
Regards, Freddie.
I’ve just done exports more carefully and in line with the SHA I quoted. Everything is working. Well, ParaView is playing up opening the files, but it’s another matter altogether. I think I must have exported the outputs of the average plugin with some previous SHA or there was some other inconsistency at the time. Apologies for the false alarm.