Please do not add the tarballs of the data to the actual (git version controlled) www repository of the website b/c git will download the full history (incl. all updated tar.gz files) when one clones the repository.
This way (depending on the compiler used of course) people trying out the gallery example can download the sample results and compare.
I believe the sample data tends to contain plot scripts etc as well, it would be great if the new downloads also contained all such extra material.
Roland, why should the data be replaced? Has it changed? I don't see a reason to replace the existing data if it hasn't changed. It is likely slightly different due to being run with a different compiler, machine, etc, but that is no reason to update the data.
We just uploaded the new data and updated the website.
@ianhinder the tarfiles each contain the date when they were created. No data is updated, instead it is added. The idea is to give a dataset that was produced with the current release. I do expect that there will be slight differences depending on compiler etc. I would rather have a dataset that documents "this was the data that the person who claimed to have run the test saw" rather than having the data slowly drift away from the data produced by the newest compiler on the newest machine with the newest release. The tarballs are all kept here: https://bitbucket.org/einsteintoolkit/www/downloads/ I see no harm (other than using space on btibucket's servers) in updating the data files so updating them would seem the less troublesome option.
The Original par file and the one with the Presync option seem to generate the same X-Y figure, files about the same size, etc. Runtimes are very similar. For our Vanderbilt ACCRE cluster with 8 MPI tasks and 8 CPUs runtime is about 5 minutes.
Running VisIt you can restore the attached session files. Here the 8 files u.file_N.h5 with N=0…7 are the 3D “database” files of format CarpetHPDF5. However if you did not run with 8 MPI tasks (?) or have a different file structure than this run, you will have to create the plot with VisIt manually. The following should get you pretty close:
singularityrundocker://symerio/visitAndiscurrentlyversion2.12.3.Youcanrestorethe*.sessionfile,orifyourfilestructureisdifferentdothefollowing"by hand."oStartVisIT;oSourcesOpenfilenamelikeu.file.*asdatabaseandselectmanuallyCarpetHDF5asfiletype.oPlotsAddPseudocolor.Loadthedataiscalled"LLAMAWAVETOY--u_lp_MP_rp_".oOnPseudocoloraddoperatorSlice.oClickDraw.Thedefaultsarenotgoodandnotethisisamovieandweshowthetimestampis5.04,Cycle56.oAlsoclickthe"Swap foreground / background colors"iconontheDrawingwindow---icon with white upper triangle and black lower triangle.oDoubleclickonthePseudocolorandselectthe"orangehot"ColorTable,andsettheminimumto-0.5andmaximumto+0.5.oDoubleclickontheSliceandselectNormal>OrthogonalZAxistoshowtheX-Yslice.oFromthemaincontrols,youcanrunthemovieorusetheslidertoselectaframe,weshowframe0056onthewebpage.
Had trouble with the curl command and the web page Add Files did not work for the tarball. Found Roland’s suggestion from November 2020 for me, which is to create the APP Password while logged on as email@example.com (my SSO) but to use the username “wegabella” so like (-v for verbose)
Run was successful yesterday. Created the images and checked the VisIT singularity command, all good. Updated the web page; they were minor changes. Also used the “git config pull.rebase false” for the merge strategy, then the “git pull” then I could “git push” (after “git add [the new files]” and “git commit -m [text]” ).
Also uploaded the tarball. Created the Bitbucket APP Password using my Vanderbilt SSO login. Still had to do the curl from my laptop. Did not work from our computing cluster. Curl command below, and cut and paste the APP Password from dumb text editor when asked.