-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Visualising PECUBE Output #12
Comments
Seems like a good idea. Could you give us a link to the PECUBE code, and in particular, it's output format? Do you do simulations in cartesian coordinates, or are they in |
Link to original PECUBE source code by Jean Braun: There you'll find documentation of output formats as well as examples. As mentioned, we've heavily modified J. Braun's version and work with different, Tübingen specific input and output files. |
It seems if PECUBE also writes out CSV files. If that is the case, we can handle that relatively easily once we know how it is organized. Handling the VTK files that are apparently also generated should also not be such a big issue. For the binary output files, the PECUBE manual states:
|
yes, it would indeed be helpful if you can explain us better how you actually use it, and what would be the ideal requirements. Write topography of a certain location as input for PECUBE? |
One problem with us (Tübingen in particular, and probably many other thermochronology groups) using PECUBE is that input/output files are not standardised, somewhat based on J. Braun's original code. Perhaps a better solution would be if you provide a general output format that is best suitable for you and that we in the thermochronology community will follow when using the GeophysicalModelGenerator, say a CSV file with [x,y,z,age1,age2,etc]. I then could provide you with a suitably formatted output of one of my recent Alps 2D sections for testing. Here in Tübingen we primarily apply PECUBE to 2D sections at the moment (can theoretically extend that to 3D). We produce two primary PECUBE output types: temperature [x, y, z, temperature] and surface age prediction [x,y,surface_elevation,age1,age2,etc]. This general format should be common across the community. Regarding topography: we usually provide a [x,y,z] user topography file as input sometimes tied to an UTM coordinate. This is not necessarily the present-day surface topography because our topography is often based on external topography modelling. |
Could you perhaps write a small Julia scripts that reads in your CSV file? Have a look at the first example. |
Attaching a simple Julia script that reads in our Tübingen-specific PECUBE temperature ([x,y,z,T]) and age ([x,y,z,AHe,AFT,ZHe,ZFT,MAr]) output files into Julia. I'm also attaching the original output files (tecplot *.dat files). Note, cartesian coordinates still need to be translated into longitude/latitude coordinates for Paraview Output in the GeophysicalModelGenerator. The data were modelled along the TRANSALP transect, WGS coordinates: |
Great thanks, I will have a look! Do you want to make a tutorial out of it that we can put in the documentation? I can also help you with that. |
As you will see, it's an extremely simple script (and only works for Tübingen specific PECUBE output). I'm not sure if it warrants a dedicated tutorial page. Perhaps by adding longitude/latitude coordinate conversion and creation of a Paraview file (similar to the example page that Boris linked) could work as an individual tutorial page though. Let me know. |
Hi Boris & Marcel,
It would be helpful to visualise PECUBE thermal output incl. age prediction on the surface. I could provide our Tübingen specific output files if needed but as you suggested it's probably better to look at the output from J. Braun's original code.
Alternatively, we formatted our output as Tecplot files. So maybe a general Tecplot file wrapper would be helpful?
Otherwise, really cool work!
Cheers,
Paul
The text was updated successfully, but these errors were encountered: