Closed dosoe closed 1 month ago
hi Dorian,
i think these changes are expected as version 8.1 deals slightly different with projecting geographic positions onto a geocentric framework. version 8.0 by default "corrects" geographic positions even for a spherical mesh. version 8.1 only converts geographic to geocentric if the mesh is actually elliptic. given your example above uses a spherical mesh, the positioning of source and receivers will be slightly different in version 8.0 and 8.1.
as a general suggestion, use the most recent version for GLOBE, i.e. version 8.1.0. this newest version will improve outputs, in particular how ellipticity and topography are incorporated when positioning sources & receivers. thus, for any code development, start from the latest devel branch version.
Ok, but I have a problem then: I am integrating semucb into specfem and I check the results by comparing it with our 'homegrown' fork of specfem3d_globe where we have integrated semucb. However, checking if I did so correctly relies on running the same model in both codes and checking if the results match. Right now the results don't match even when running prem, so I cannot use this method to check whether I integrated semucb correctly. Should I run my tests with the ellipticity enabled, so that both use an elliptic mesh? So far I have disabled all additional factors ( ellipticity, rotation etc) to make it simpler to diagnose problems should they arise.
Running the same tests with ellipticity enabled gives a perfect fit. I believes that settles this.
Description
I have run specfem3d_globe for the main and the devel branches for an event and a handful of stations and the results are not matching between the two runs. Here is a plot of the output, comparing the results for the mentioned event and stations (see reproduction steps) with the outputs filtered with the same filter, a bandpass with corner periods 500, 400, 50 and 40 seconds. Black is specfem3d_globe 8.0, red is 8.1 (devel branch, both were cloned today 16/09/2024) and blue is the difference. Both red and black curves have been normalised by the maximum of the black curve. As can be seen, there is a significant discrepancy between the two.
I can provide the plotting code it requested, as well as the full logs.
This is problematic for me because I am attempting to include another model into specfem and I need to benchmark it. I have been told to use the devel branch, but if the outputs of devel are incorrect, it is impossible for me to benchmark the results.
Affected SPECFEM3D_GLOBE version
8.0 and 8.1
Your software and hardware environment
Run on cluster Anvil on 3 nodes (384 cores), compilers openmpi/4.0.6, intel/19.0.5.281
Reproduction steps
Screenshots
Logs
OS
No response