sceccode / bbp Goto Github PK

Update the SDSU BBToolbox module to version 1.6.2, as per SDSU's instructions. See comments below. Update the Fortran codes and test the updated module.

Main changes are 2 parts.

(1) coda energy envelope computation change, mainly in coda.f90. This change will improve synthetic accelerations in the time domain, but not change SA bias plots significantly.

(2) add shifting scattgram according to the minimum initiation time from srf file. This change will improve simulations for multiple segment ruptures, and change SA bias plots for 3-segment-rupture for Landers.

Update the science documentation for each of the methods in the Broadband Platform with the updated 1-page descriptions provided by each of the modeling groups.

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

@fabiolsilva, I had been using the FAS module to compute FAS for simulations where I was not comparing with any observations. This commit to the FAS module now breaks it if observations aren't supplied:

646b247

I get this stack trace at first:

Traceback (most recent call last):
  File "/project/scec_608/kmilner/bbp/dev/bbp/comps/run_bbp.py", line 304, in <module>
    obj = item.instantiate(sim_id)
  File "/project/scec_608/kmilner/bbp/dev/bbp/comps/module.py", line 134, in instantiate
    return globals()[self.module_name](*self.module_args, **self.kw_args)
TypeError: __init__() missing 1 required positional argument: 'i_comparison_label'

I then tried changing the init method to default i_comparison_label to None, but get a new one:

Traceback (most recent call last):
  File "/project/scec_608/kmilner/bbp/dev/bbp/comps/run_bbp.py", line 305, in <module>
    obj.run()
  File "/project/scec_608/kmilner/bbp/dev/bbp/comps/fas.py", line 836, in run
    obs_dt = read_bbp_dt(input_obs_acc_file)
  File "/project/scec_608/kmilner/bbp/dev/bbp/comps/fas.py", line 339, in read_bbp_dt
    input_file = open(bbp_file)
FileNotFoundError: [Errno 2] No such file or directory: '/tmp/SLURM_3430421/tmpdata/11127002307386261/obs_seis_USC/USC.bbp'

I need this working soon, so I'll start throwing a bunch of if statements in there to isolate the observation code, but thought I would give you the chance to do it if you would prefer and can get to it in the next day or so. Thanks!

Kevin

The private instillation link is difficult to find. Make it easier for users to find where to get the complete installation script.

https://scec.usc.edu/it/Broadband_Easy_Install_v17.3.0

BBP documentation been developed over several years, and documents posted on SCEC websites. Review the BBP documents and wiki entries and remove duplicate and misleading information and files.

The user is presented with velocity model names as they configure a simulation.

Users asked us to present the user with different names for these velocity models.

For the CEUS and CENA, user asked us to number them (CEUS001, CEUS002, CENA001, etc.) and have a longer description somewhere for what they consist of

Please select a velocity model (either number or name is ok):

(1) CEUS1k
(2) CentralJapan
(3) Canada1k
(4) CentralUS
(5) NOCAL
(6) LABasin
(7) WesternJapan
(8) Mojave
?
...

SCEC engineers have defined a series of evaluation tests to be run for each release. Add a link to the evaluation process, and to the evaluation results for new BBP release.

The wiki page for "Running Simulations" states:

Metadata capturing all the executable calls is located in tmpdata/<simulation ID>/metadata.txt for careful tracing of exactly what was called. Both the log files and metadata can be useful if troubleshooting an issue.

But this file isn't being created. No file named 'metadata.txt' is generated anywhere in the bbp_data file tree.

I'm experiencing intermittent failures on the HF part of the GP calculation with the attached inputs. I originally believed that it was dependent on the seed, but failure is intermittent with the same seed. The attached inputs failed in 2 of 10 tries.

Current dev branch on Xubuntu 16.4.

Here is the output:

------------------------------------GP Jbsim------------------------------------
==> Generating LF seismogram for station: USC
==> Generating LF seismogram for station: SBSM
-------------------------------GP Jbsim Completed-------------------------------

-----------------------------------GP HfSims------------------------------------
Running: /home/kevin/bbp/dev/bbp/src/gp/bin/srf2stoch infile=/home/kevin/bbp/bbp_data/indata/6121001/event_145982_0.1s_CONST_VEL_ADJ_LEN.srf outfile=/home/kevin/bbp/bbp_data/tmpdata/6121001/event_145982_0.1s_CONST_VEL_ADJ_LEN.srf.stations_cs_sites.2.000000x2.000000 target_dx=2.000000 target_dy=2.000000 >> /home/kevin/bbp/bbp_data/logs/6121001/6121001.hfsims_stations_cs_sites.log 2>&1
Running: /home/kevin/bbp/dev/bbp/src/gp/bin/hb_high_v5.4.3 >> /home/kevin/bbp/bbp_data/logs/6121001/6121001.hfsims_stations_cs_sites.log 2>&1 << END
50
/home/kevin/bbp/bbp_data/indata/6121001/stations_cs_sites.stl
/home/kevin/bbp/bbp_data/tmpdata/6121001/tmp_hfsim_out
2 1 2
1
4 0 0.02 19.9
12345523
2
102.400000 0.010000 10.000000 0.040000 0.600000
0.841246 0.700000 1.000000 0.000000 0.100000
-1 -1.000000
/home/kevin/bbp/bbp_data/tmpdata/6121001/event_145982_0.1s_CONST_VEL_ADJ_LEN.srf.stations_cs_sites.2.000000x2.000000
/home/kevin/bbp/bbp_data/indata/6121001/genslip_nr_generic1d-gp01.vmod_stations_cs_sites.local
999.900000
-99 0.0 0.0 0.0 0.0 1
-1
0.000000 0.0 0.000000
0
END
------------------------------GP HfSims Completed-------------------------------

-------------------------------------Match--------------------------------------
==> Processing velocity seismograms for station: USC
==> Processing acceleration seismograms for station: USC
Traceback (most recent call last):
  File "/home/kevin/bbp/dev/bbp/comps/run_bbp.py", line 295, in <module>
    obj.run()
  File "/home/kevin/bbp/dev/bbp/comps/match.py", line 465, in run
    print_cmd=False)
  File "/home/kevin/bbp/dev/bbp/comps/bband_utils.py", line 85, in runprog
    (cmd, proc.returncode))
BroadbandExternalError: None

/home/kevin/bbp/dev/bbp/src/gp/bin/wcc_resamp_arbdt newdt=0.010000 pow2=0 infile=/home/kevin/bbp/bbp_data/tmpdata/6121001/6121001.USC-hf.acc.000 outfile=/home/kevin/bbp/bbp_data/tmpdata/6121001/6121001.USC-hf-resamp.000 >> /home/kevin/bbp/bbp_data/logs/6121001/6121001.match_stations_cs_sites.log 2>&1 returned 139

Update Broadband Platform license to BSD-3, replace license text from all USC source files.

Modify the seismogram plotting scripts to better handle cases where the time series contain a large leading and/or trailing area of inactivity. Plotting the entire time series for a 400s long file, will generate a plot with very little detail that is not very useful. One possible solution would be estimating the start of the activity using the station distance from the rupture to guess when to start plotting. Another idea is to use Arias intensity to detect the start/end of the activity and then add a buffer on both sides.

Post updated validation and region packages, update the Broadband Platform version number.

I have an existing SRF file that I want to use, running the platform in simulation mode.

The documentation (under Running Simulations, User-defined Simulations) states:

To run a user-defined simulation, two input files are required, a source description (src file) and a station list (stl file). For certain methods, the source description can either be in SRF format or a simple source description (the format is described in File Formats).

However I get this message when selecting an SRF as my source file:

Enter path and filename of source description: /home/kevin/bbp/bbp_data/run/event_136704_0.05s_ADJ_VEL.srf
File /home/kevin/bbp/bbp_data/run/event_136704_0.05s_ADJ_VEL.srf not found or invalid source description, please re-enter

Additionally, SRF files do not show up in the list when choosing the select a source description in /home/kevin/bbp/bbp_data/run option. This makes me think that maybe I'm supposed to create a SRC file, and somehow tell it the path to the SRF. However there is no mention of a field for specifying a SRF path in the File Format Guide section on the SRC files.

I am using BBP to get some results of a downhole array, but when I look into the file format guide, There is no "depth" option for the STL file. Is there any way to set a depth parameter for stations? Thanks!

In newer Python/Numpy versions the RMG module fails due to some float indexes. Change these variable types to integer when they are used as array indexes and validate the change doesn't affect the results.

Here's the output of the unit test:

$ ./test_rmg.py
test_rmg (__main__.TestRMG) ... Running: cp /home/song/proj/GM_Sim/SCEC_BBP/bbp_17.3.0/bbp-17.3.0/bbp/tests/ref_data/song/test_whittier_song.src /home/song/proj/GM_Sim/SCEC_BBP/bbp_17.3.0/bbp_data/indata/8239555
---------------------------SONG Rupture Generator RMG---------------------------

### Step I: 2-point statistics
### generating 2D distributions of source parameters
### based on covariance matrix constructed from
### auto- and cross-correlation


=> Number of subfaults (fine grid): 10000
=> Number of subfaults (coarse grid): 729

=> Elapsed time for constructing Cm:       0.23
=> Elapsed time for Eigen decomposition:      39.89
=> Elapsed time for Cholesky Factorization:       0.15
ERROR

======================================================================
ERROR: test_rmg (__main__.TestRMG)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "./test_rmg.py", line 59, in test_rmg
    rmg.run()
  File "/home/song/proj/GM_Sim/SCEC_BBP/bbp_17.3.0/bbp-17.3.0/bbp/comps/rmg.py", line 1284, in run
    self.gen_rup()
  File "/home/song/proj/GM_Sim/SCEC_BBP/bbp_17.3.0/bbp-17.3.0/bbp/comps/rmg.py", line 994, in gen_rup
    self.gen_dist()
  File "/home/song/proj/GM_Sim/SCEC_BBP/bbp_17.3.0/bbp-17.3.0/bbp/comps/rmg.py", line 816, in gen_dist
    (rup["nz1"], rup["nx1"]), order='F')
  File "/usr/local/lib/python-2.7.13/lib/python2.7/site-packages/numpy/core/fromnumeric.py", line 232, in reshape
    return _wrapfunc(a, 'reshape', newshape, order=order)
  File "/usr/local/lib/python-2.7.13/lib/python2.7/site-packages/numpy/core/fromnumeric.py", line 67, in _wrapfunc
    return _wrapit(obj, method, *args, **kwds)
  File "/usr/local/lib/python-2.7.13/lib/python2.7/site-packages/numpy/core/fromnumeric.py", line 47, in _wrapit
    result = getattr(asarray(obj), method)(*args, **kwds)
TypeError: 'float' object cannot be interpreted as an index

----------------------------------------------------------------------
Ran 1 test in 40.599s

FAILED (errors=1)

Create a short wiki entry on describing principles used by each method. Enable wiki so that model developers can add material to their entries as needed.

The older BBP wiki entries should be updated to note that there is a more recent version of the BBP available on github.

Create a new wiki entry that describes how to use the new multi-segment capabilities of BBP.

I have created a SRF file for a single station using BBP. Later on, I want to use that SRF as input for another run using exactly the same input files (station list, velocity model, etc). However, at the very end, the program gives me the following error,

<
-------------------------------------Match--------------------------------------
==> Processing acceleration seismograms for station: SBEB
--------------------------------Match Completed---------------------------------

------------------------------------Plot MAP------------------------------------
Traceback (most recent call last):
File "/mnt/usuarios/aaron/BBP/bbp-master/bbp/comps/run_bbp.py", line 295, in
obj.run()
File "/mnt/usuarios/aaron/BBP/bbp-master/bbp/comps/plot_map.py", line 75, in run
a_input_file)
File "/mnt/usuarios/aaron/BBP/bbp-master/bbp/comps/plot_utils.py", line 181, in set_boundaries_from_stations
lat1, lon1, _, _, lat2, lon2 = calculate_fault_edges(a_src_file)
File "/mnt/usuarios/aaron/BBP/bbp-master/bbp/comps/plot_utils.py", line 120, in calculate_fault_edges
raise bband_utils.ParameterError("SRC file missing fault_length!")
ParameterError: SRC file missing fault_length!

Ask SCEC web or AWS team members to identify methods for automating the creation of BBP virtual images, and use them to create 17.3 images.

I'm running the easy_install_bbp.sh script for the current dev branch. It compiles successfully (yay!) but runs into problems when you get to the velocity models section:

kevin@steel:~/git/bbp/setup$ ./easy_install_bbp.sh 
./easy_install_bbp.sh: 47: ./easy_install_bbp.sh: Bad substitution

 ====== Welcome to Broadband Platform 17.3.0 installation script =====

 Using destination directory: /home/kevin/git

=> Creating directory tree...

=> Main Broadband Platform Source Distribution
==> Compiling... (it may take a while)
==> Installed!

 Please select what velocity models (regions) you would like to install:

==> Would you like to install the Northern California region (6.5GB)?
./easy_install_bbp.sh: 120: ./easy_install_bbp.sh: select: not found
./easy_install_bbp.sh: 125: ./easy_install_bbp.sh: Syntax error: "done" unexpected

Also note the "Bad substitution" message at the top.

This is on linux, Xubuntu 16.04 LTS.

Please note that your geoutm() routine provided to convert long/lat to UTM coordinates contains two 2 mistakes:

source file: geo_utm.f

line 98:

wrong: f3=15.d0*e4/256.d0*45.d0*e6/1024.d0
correct would be: f3=15.d0*e4/256.d0 + 45.d0*e6/1024.d0

line 163

wrong: f3=5.d0*3.d0*t1+10.d0*c1-4.d0*c1**2-9.d0*ep2
correct would be: f3=5.d0 + 3.d0*t1+10.d0*c1-4.d0*c1**2-9.d0*ep2

the above corrections could be verified by looking at the original publication:
Snyder, J.P., Map projections - a working manual, USGS professional paper 1395, 1987
https://doi.org/10.3133/pp1395

line 98 mistake/correction: see page 61, eq. 3-21 for M
line 163 mistake/correction: see page 63, eq. 8-17 for phi

the above error will lead to a positional error of ~7 m when converting lon/lat to UTM.

best regards,
daniel

when building the current dev branch, the bbp/tests/UnitTests.py script fails. These tests are important for users to confirm their installation is working correctly.

The unit test test_rmg fails on Summit:

ERROR: test_rmg (test_rmg.TestRMG)

Traceback (most recent call last):
File "/gpfs/alpine/geo112/proj-shared/CyberShake/software/bbp/bbp-19.8.0-python3/bbp/tests/test_rmg.py", line 67, in test_rmg
rmg.run()
File "/gpfs/alpine/proj-shared/geo112/CyberShake/software/bbp/bbp-19.8.0-python3/bbp/comps/song_rmg_single_seg.py", line 1295, in run
self.gen_rup()
File "/gpfs/alpine/proj-shared/geo112/CyberShake/software/bbp/bbp-19.8.0-python3/bbp/comps/song_rmg_single_seg.py", line 1005, in gen_rup
self.gen_dist()
File "/gpfs/alpine/proj-shared/geo112/CyberShake/software/bbp/bbp-19.8.0-python3/bbp/comps/song_rmg_single_seg.py", line 801, in gen_dist
L = np.linalg.cholesky(cm)
File "/sw/summit/python/3.6/anaconda3/5.3.0/lib/python3.6/site-packages/numpy/linalg/linalg.py", line 614, in cholesky
r = gufunc(a, signature=signature, extobj=extobj)
File "/sw/summit/python/3.6/anaconda3/5.3.0/lib/python3.6/site-packages/numpy/linalg/linalg.py", line 92, in _raise_linalgerror_nonposdef
raise LinAlgError("Matrix is not positive definite")
numpy.linalg.linalg.LinAlgError: Matrix is not positive definite

My Summit environment is:
[[email protected] tests]$ module list

Currently Loaded Modules:

1. hsi/5.0.2.p5 6) python/3.6.6-anaconda3-5.3.0
2. xalt/1.1.4 7) gcc/6.4.0
3. lsf-tools/2.0 8) spectrum-mpi/10.3.0.1-20190611
4. DefApps 9) fftw/3.3.8
5. cuda/10.1.168

Add a progress bar to the BBP installation scripts to provide users more information about what is going on during the installation process. This is useful since some package downloads can take a very long time. Make sure both wget and curl print their progress bar, and output intermediate package installation milestones so users can see things are moving during the installation process.

Hello, @Fabio Silva. I have a stupid problem when I try to install the LA Basin region data. I followed the instruction and succeeded installing for the first time, but I couldn't download it again although I repeated the instruction and I got enough space. It showed the problem as follows when I ran bash easy_install_bbp_19.4.0.sh:

=> Installing Broadband Platform Velocity Model Packages
==> LA Basin
tar (child): labasin500-velocity-model-19.4.0.tar.gz：Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now
md5sum: labasin500-velocity-model-19.4.0.tar.gz: No such file or directory

=> ERROR! MD5SUM check failed for labasin500-velocity-model-19.4.0.tar.gz

I use Ubuntu 20.04 with VMware Workstation. My software dependencies:
Python 2.7.14 :: Anaconda, Inc.
scipy (1.2.3)
matplotlib (2.2.3)
numpy (1.16.6)
pyproj (1.9.6)
FFTW library 3.3.10
tar (GNU tar) 1.30

I checked the https://hypocenter.usc.edu/research/bbp/versions/19.4.0/*** (in the easy_install_bbp_19.4.0.sh) and failed to enter the website, showing 502 error. Should I change something in easy_install_bbp_19.4.0.sh file to solve this problem? Thank you in advance for reviewing.

SCEC web developers determined it looks like detailed tracking is currently not possible. We cannot add JavaScript to pages displayed when you land on your repository so google analytics can't be added that way.

See this GitHub issue requesting to allow google analytics on repositories:
isaacs/github#446

GitHub does provide data on the last 14 days of traffic. The data it exposes is listed here:
https://help.github.com/articles/viewing-traffic-to-a-repository/

There have been attempts to game the system using a tracking image and google analytics. The idea is to add an image in your readme.md (which is the text that is displayed when you land on a repository) coming directly from a server you control thus providing some tracking data. I tested adding an image from scec.org but GitHub seems to serve it from a CDN so it doesn't seem promising. In any case, here's detail on that method:

• https://www.sitepoint.com/using-beacon-image-github-website-email-analytics/
• https://github.com/igrigorik/ga-beacon

Recently, GitHub exposed the traffic data they collect via a JSON API. A script could be created to poll this API periodically, storing the data ourselves thus getting around the 2-week limit. GitHub official traffic API:

https://developer.github.com/v3/repos/traffic/

This would allow at least some tracking data to be gathered over the long term. As you can see in the links above, with this API one can track top referrers, top repo paths visited, visitors, unique visitors, and clones.

Could you please explain how the fault geometry is incorporated into EXSIM and the method for generating 3-component accelerograms? Many thanks!

Once the BBP installation completes, the following addition to the user's .bash_profile is recommended:

export PYTHONPATH=/gpfs/alpine/proj-shared/geo112/CyberShake/software/bbp/bbp-19.8.0-python3/bbp/comps

However, this will overwrite any custom PYTHONPATH modifications the user has made. I suggest changing this to:

export PYTHONPATH=/gpfs/alpine/proj-shared/geo112/CyberShake/software/bbp/bbp-19.8.0-python3/bbp/comps:${PYTHONPATH}

Hello, I have a strong question about the Graves and Pitarka model (GP). How made the combination between the individual low- and high-frequency responses into a single broadband time series using a set of matched fourth order Butterworth filters having a common corner frequency of 1 Hz? Please can you share the formulations?

Thanks

Please give credit to Karen Assatourians, Western University, for the original bbp_converge script.

https://github.com/SCECcode/bbp/blob/dev/bbp/utils/batch/bbp_converge.py

One of our researchers ran the unit test and got the error

======================================================================
FAIL: test_genslip_fftw (test_genslip.TestGenslip)
Test GP rupture generator for the correct FFTW behavior
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/project/6001152/bbp/bbp-22.4.0/bbp/tests/test_genslip.py", line 132, in test_genslip_fftw
    self.assertFalse(not cmp_bbp.cmp_srf(a_ref_file, a_newfile,
AssertionError: True is not false : Output file /home/tyson/projects/def-tyson/bbp/bbp_data/tmpdata/5201715/5201715_nr_eq.srf does not match reference file /home/tyson/projects/def-tyson/bbp/bbp-22.4.0/bbp/tests/ref_data/gp/m6.73-0.10x0.10_s2379646.srf

Running the comparison manually gives (is there any way to get the output from the cmp_bbp routine from the unit test script?)

Plane 0, point 186: point parameters in field 4 disagree.

The relevant lines from the files are

 -118.434769   34.303387  5.16943e+00  116   44  1.00000e+08  8.352078e+00  1.00000e-01   3.35000e+05   2.70000e+00
  79    77.4399     23     0.0000      0     0.0000      0

 -118.434769   34.303387  5.16943e+00  115   44  1.00000e+08  8.352078e+00  1.00000e-01   3.35000e+05   2.70000e+00
  79    77.4399     23     0.0000      0     0.0000      0

so it seems the issue is that the strike angle disagree by 1 degree.

Examining the cmp_bbp routine reveals they are expected to agree to PP_TOLERANCE = 0.011, which is pretty meaningless given they are only output to the degree. Seems there should either at least two decimals output or an ANGLE_TOLERANCE = 1 added and used to compare strike and dip.

Add an option to cluster scripts (both scenario and validation scripts) to enable users to specify the number of cores to be used per node. This is useful to limit the number of concurrent BBP jobs launched at each node and avoid running out of memory issues.

In the Broadband Platform, 1D velocity model are available for just few regions. But I want to research other regions, can I use the user-defined velocity files? And how to set the file?

The BBToolbox unit test fails on Summit:

FAIL: test_bbtoolbox (test_bbtoolbox.TestBBToolbox)

Traceback (most recent call last):
File "/gpfs/alpine/geo112/proj-shared/CyberShake/software/bbp/bbp-19.8.0-python3/bbp/tests/test_bbtoolbox.py", line 90, in test_bbtoolbox
(ref_file))
AssertionError: True is not false : output HF BBP /gpfs/alpine/proj-shared/geo112/CyberShake/software/bbp/bbp_data/tmpdata/854229/854229.s02.bbp file does not match reference hf bbp file /gpfs/alpine/proj-shared/geo112/CyberShake/software/bbp/bbp-19.8.0-python3/bbp/tests/ref_data/sdsu/s02.bbp

My Summit environment is:
[[email protected] tests]$ module list

Currently Loaded Modules:

1. hsi/5.0.2.p5 6) python/3.6.6-anaconda3-5.3.0
2. xalt/1.1.4 7) gcc/6.4.0
3. lsf-tools/2.0 8) spectrum-mpi/10.3.0.1-20190611
4. DefApps 9) fftw/3.3.8
5. cuda/10.1.168

The current SRF plotting scripts on the BBP cannot handle long thin ruptures very well. The resulting plots are often just a black band that provides very little useful information.

In addition to using portrait mode, for ruptures that have an elongated aspect ratio, consider dividing the the rupture into segments and plotting multiple segments separately on the same page one above the other.

Hello Dev Team,

I am having an issue with installation, it appears to be an issue with the Fortran compiler (please see below). I am running Umbunto 22.04.3 lts Jammy Jellyfish. I used the easy installation script. I tried FCFLAGS and FFLAG from a similar issue but with a different program ex. (not entirely sure if I entered these correctly; https://forum.mmm.ucar.edu/threads/how-to-fix-rank-mismatch-between-actual-argument-at-1-and-actual-argument-at-2-scalar-and-rank-1.14995/); Thank you for your help.:

export fallow_argument=-fallow-argument-mismatch
export boz_argument=-fallow-invalid-boz
export FFLAGS="$fallow_argument $boz_argument -m64"
export FCFLAGS="$fallow_argument $boz_argument -m64"

./easy_install_bbp_22.4.0.sh

====== Welcome to Broadband Platform 22.4.0 installation script ======

Using destination directory: /home/dewan/Desktop/bbp

==> Creating directory tree...

====== Setting up FFTW 3.3.8 library,... it takes a minute..... ======

===> Downloading...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 4013k 0 4013k 0 0 1244k 0 --:--:-- 0:00:03 --:--:-- 1244k
===> Uncompressing file...
===> Checking md5sum...
===> Building single-precision library...
===> Building double-precision library...
===> Cleaning up...
==> FFTW Built successfully!

====== Setting up Broadband Platform 22.4.0 Source Distribution ======

==> Compiling... (it may take a few minutes)

****** ERROR: BBP build failed, for more details please check:
****** ERROR: /home/dewan/Desktop/bbp/bbp-22.4.0/bbp/src/bbp-build.log

LOG FILE-
gfortran -O3 -c -o GOF_MO.o GOF_MO.f
GOF_MO.f:526:17:

512 | call GOF(ABS(ASx), ABS(ARx), nt2, 1, nt2, LSaccX)
| 2
......
526 | call GOF(PGAxR, PGAxS, 1, 1, 1, PGAfitX)
| 1
Error: Rank mismatch between actual argument at (1) and actual argument at (2) (rank-1 and scalar)
GOF_MO.f:527:17:

512 | call GOF(ABS(ASx), ABS(ARx), nt2, 1, nt2, LSaccX)
| 2
......
527 | call GOF(PGAyR, PGAyS, 1, 1, 1, PGAfitY)
| 1
Error: Rank mismatch between actual argument at (1) and actual argument at (2) (rank-1 and scalar)
GOF_MO.f:528:17:

512 | call GOF(ABS(ASx), ABS(ARx), nt2, 1, nt2, LSaccX)
| 2
......
528 | call GOF(PGAzR, PGAzS, 1, 1, 1, PGAfitZ)
| 1
Error: Rank mismatch between actual argument at (1) and actual argument at (2) (rank-1 and scalar)
GOF_MO.f:531:17:

512 | call GOF(ABS(ASx), ABS(ARx), nt2, 1, nt2, LSaccX)
| 2
......
531 | call GOF(PGVxR, PGVxS, 1, 1, 1, PGVfitX)
| 1
Error: Rank mismatch between actual argument at (1) and actual argument at (2) (rank-1 and scalar)
GOF_MO.f:532:17:

512 | call GOF(ABS(ASx), ABS(ARx), nt2, 1, nt2, LSaccX)
| 2
......
532 | call GOF(PGVyR, PGVyS, 1, 1, 1, PGVfitY)
| 1
Error: Rank mismatch between actual argument at (1) and actual argument at (2) (rank-1 and scalar)
GOF_MO.f:533:17:

512 | call GOF(ABS(ASx), ABS(ARx), nt2, 1, nt2, LSaccX)
| 2
......
533 | call GOF(PGVzR, PGVzS, 1, 1, 1, PGVfitZ)
| 1
Error: Rank mismatch between actual argument at (1) and actual argument at (2) (rank-1 and scalar)
GOF_MO.f:536:17:

512 | call GOF(ABS(ASx), ABS(ARx), nt2, 1, nt2, LSaccX)
| 2
......
536 | call GOF(PGDxR, PGDxS, 1, 1, 1, PGDfitX)
| 1
Error: Rank mismatch between actual argument at (1) and actual argument at (2) (rank-1 and scalar)
GOF_MO.f:537:17:

512 | call GOF(ABS(ASx), ABS(ARx), nt2, 1, nt2, LSaccX)
| 2
......
537 | call GOF(PGDyR, PGDyS, 1, 1, 1, PGDfitY)
| 1
Error: Rank mismatch between actual argument at (1) and actual argument at (2) (rank-1 and scalar)
GOF_MO.f:538:17:

512 | call GOF(ABS(ASx), ABS(ARx), nt2, 1, nt2, LSaccX)
| 2
......
538 | call GOF(PGDzR, PGDzS, 1, 1, 1, PGDfitZ)
| 1
Error: Rank mismatch between actual argument at (1) and actual argument at (2) (rank-1 and scalar)
GOF_MO.f:574:17:

512 | call GOF(ABS(ASx), ABS(ARx), nt2, 1, nt2, LSaccX)
| 2
......
574 | call GOF(MAXVAL(SRSX), MAXVAL(SRRX), 1, 1, 1, PSAfitX)
| 1
Error: Rank mismatch between actual argument at (1) and actual argument at (2) (rank-1 and scalar)
GOF_MO.f:575:17:

512 | call GOF(ABS(ASx), ABS(ARx), nt2, 1, nt2, LSaccX)
| 2
......
575 | call GOF(MAXVAL(SRSY), MAXVAL(SRRY), 1, 1, 1, PSAfitY)
| 1
Error: Rank mismatch between actual argument at (1) and actual argument at (2) (rank-1 and scalar)
GOF_MO.f:576:17:

512 | call GOF(ABS(ASx), ABS(ARx), nt2, 1, nt2, LSaccX)
| 2
......
576 | call GOF(MAXVAL(VSRR), MAXVAL(VSRS), 1, 1, 1, PSAfitZ)
| 1
Error: Rank mismatch between actual argument at (1) and actual argument at (2) (rank-1 and scalar)
GOF_MO.f:643:15:

512 | call GOF(ABS(ASx), ABS(ARx), nt2, 1, nt2, LSaccX)
| 2
......
643 | call GOF(DHR, DHS, 1, 1, 1, DFX)
| 1
Error: Rank mismatch between actual argument at (1) and actual argument at (2) (rank-1 and scalar)
GOF_MO.f:660:15:

512 | call GOF(ABS(ASx), ABS(ARx), nt2, 1, nt2, LSaccX)
| 2
......
660 | call GOF(DHR, DHS, 1, 1, 1, DFY)
| 1
Error: Rank mismatch between actual argument at (1) and actual argument at (2) (rank-1 and scalar)
GOF_MO.f:677:15:

512 | call GOF(ABS(ASx), ABS(ARx), nt2, 1, nt2, LSaccX)
| 2
......
677 | call GOF(DHR, DHS, 1, 1, 1, DFZ)
| 1
Error: Rank mismatch between actual argument at (1) and actual argument at (2) (rank-1 and scalar)
make[2]: *** [makefile:36: GOF_MO.o] Error 1
make[2]: Leaving directory '/home/dewan/Desktop/bbp/bbp-22.4.0/bbp/src/sdsu/MOGof'
make[1]: *** [makefile:5: all] Error 2
make[1]: Leaving directory '/home/dewan/Desktop/bbp/bbp-22.4.0/bbp/src/sdsu'
make: *** [makefile:3: all] Error 2

The SCEC.org website should have a landing page describing the BBP and leading to the BBP documentation, and source code.

Is it possible to add RotD100 and PGV calcluations to BBP for non-validation runs? I notice that there is a RotD100 module, but it seems to be tied to validation mode.

Update License file with USC disclaimers and current year.

The wiki doesn't give any information on RotD50 units that I could find. The Running-Simulations wiki pages states:

The RotD50 code, run at the end of each simulation, calculates the response spectra for each station. The raw RotD50 data is located at

outdata/<simulation ID>/<simulation ID>.<station>.rd50

in the format described in File Formats.

Except the "File Formats" section doesn't mention this file, nor it's units. The "Data Products" page, while not linked above, does include an example of the .rd50 files, but does not mention units.

Please reply to this issue with the units ASAP, even if it takes longer to fix the wiki and close it. I imagine they will be in g or cm/s^2. Thanks!

The SRC file format description needs to be completed. Currently UNITS is missing. Review to make sure all information in SRC file format exchange is included in wiki entry.

When running the unit tests on OLCF Summit, a seg fault occurs on line 406:

*ptr++ = c;

I believe this is because C type 'char' on Summit defaults to 'unsigned char', but EOF is defined as -1, so an unsigned char will never be equal to EOF. Therefore, the while loop in line 400 will never exit, and eventually ptr will overflow far enough to cause a seg fault.

Potential solutions include changing c to a signed char (which can hold any ASCII filenames), testing the file pointer for EOF rather than the character, or changing from readline() to a more standard C function such as fscanf().