Publishing UCERF3-ETAS Event Reports - Revision history

Bhatthal: /* Publishing the UCERF3-ETAS Forecast */

2026-04-08T20:48:03Z

Publishing the UCERF3-ETAS Forecast

Bhatthal: Add link to SCEC Event Page Troubleshooting

2025-11-16T21:32:13Z

Add link to SCEC Event Page Troubleshooting

Bhatthal: /* Quakeworx */ Add Scott's drupal id

2025-10-16T17:24:26Z

Quakeworx: Add Scott's drupal id

Bhatthal: Rename event-reports repo to ucerf3-etas-results

2025-07-29T00:10:24Z

Rename event-reports repo to ucerf3-etas-results

Maechlin: /* Publishing the UCERF3-ETAS Forecast */

2025-07-18T23:17:59Z

Publishing the UCERF3-ETAS Forecast

Maechlin at 18:37, 18 July 2025

2025-07-18T18:37:10Z

Bhatthal: /* Publishing the UCERF3-ETAS Forecast */ Update instructions to use SSH repo clone

2025-07-10T06:30:21Z

Publishing the UCERF3-ETAS Forecast: Update instructions to use SSH repo clone

Bhatthal: /* Publishing the UCERF3-ETAS Forecast */ Update repository to SCECcode/event-reports

2025-07-10T06:27:08Z

Publishing the UCERF3-ETAS Forecast: Update repository to SCECcode/event-reports

Bhatthal: Add Quakeworx section outlining the drupaluid IDs

2025-06-30T18:56:45Z

Add Quakeworx section outlining the drupaluid IDs

Bhatthal at 05:52, 19 March 2025

2025-03-19T05:52:11Z

@@ Line 67: / Line 67: @@
 ) Ensure that you have selected the correct Event ID and directories. See the following section for an explanation of the parameters used.
-# Set environment variables in bash config
+* Set environment variables in bash config
-* Ensure you're on an interactive node:
+* Ensure you're on an interactive node
 * Update your bash config with:
 <code>
 module load cpu/0.15.4
-module load openjdk/11.0.2
+module load openjdk/17.0.8.1_1
-ETAS_LAUNCHER=/expanse/lustre/projects/usc143/qwxdev/apps/expanse/rocky8.8/ucerf3-etas/069e27e/ucerf3-etas-launcher
+export PROJFS=/expanse/lustre/projects/usc143/$USER
-export PATH=$ETAS_LAUNCHER/sbin:$PATH
+export MPJ_HOME=$PROJFS/mpj-express
 </code>
 ) Connect to an interactive node
-<code>srun --partition=debug  --pty --account=usc143 --nodes=1 --ntasks-per-node=4 --mem=16G -t 00:30:00 --wait=0 --export=ALL /bin/bash</code>
+<code>srun --partition=debug  --pty --account=usc143 --nodes=1 --ntasks-per-node=4 --mem=32G -t 00:30:00 --wait=0 --export=ALL /bin/bash</code>
 ) Assuming you have reserved an interactive node with sufficient memory, ensure that you have sufficient memory for execution on this node.

← Older revision		Revision as of 21:32, 16 November 2025
Line 12:		Line 12:
	[[File:Malibu EQ.png\|400px\|thumb\|Fig 2. SCEC Event Page for M4 earthquake near Malibu, CA]]		[[File:Malibu EQ.png\|400px\|thumb\|Fig 2. SCEC Event Page for M4 earthquake near Malibu, CA]]
	[[File:UCERF3-ETAS Forecast in Event Page.png\|400px\|thumb\|Fig 3. UCERF3-ETAS Forecast as seen on the Event Page]]		[[File:UCERF3-ETAS Forecast in Event Page.png\|400px\|thumb\|Fig 3. UCERF3-ETAS Forecast as seen on the Event Page]]
		+
		+	For any errors generating SCEC Event Pages, refer to [[SCEC Event Page Troubleshooting]].

@@ Line 153: / Line 153: @@
 * Fabio Silva: 7
 * Akash Bhatthal: 20
 For example, a job Phil ran on Quakeworx labelled "DeepSprings_EQ" would be found at <code>/expanse/lustre/scratch/qwxdev/temp_project/qwx1/users/drupaluid_6/jobs/DeepSprings_EQ/</code>.
 In order to run the ComcatReportPageGen, you should copy this event from scratch into your own home directory. Here you can make changes to the config.json configuration as necessary and execute the generator (See step 6) with an updated etas-dir.

@@ Line 16: / Line 16: @@
 == Git Troubleshooting ==
-Pushing your changes upstream requires you to have an added SSH key on Frontera to allow you to make changes with your GitHub account. You must also use a GitHub account that is authorized to push changes directly to the event-reports/master branch.
+Pushing your changes upstream requires you to have an added SSH key on Frontera to allow you to make changes with your GitHub account. You must also use a GitHub account that is authorized to push changes directly to the ucerf3-etas-results/master branch.
 You can request edit permissions to the repository owner, Akash Bhatthal <[mailto:bhatthal@usc.edu bhattha@usc.edu]>
@@ Line 43: / Line 43: @@
 . If you cloned the repository with HTTPS instead of SSH, then you need to update your remote accordingly.<br/>
-<code>git remote set-url origin git@github.com:(your_user_name)/event-reports.git</code>
+<code>git remote set-url origin git@github.com:(your_user_name)/ucerf3-etas-results.git</code>
-. If your account has sufficient permissions, you should be able to push directly upstream to event-reports/master.
+. If your account has sufficient permissions, you should be able to push directly upstream to ucerf3-etas-results/master.
 == Publishing the UCERF3-ETAS Forecast ==
 Generate your UCERF3-ETAS forecast for a given earthquake event following instructions available at [[UCERF3-ETAS Measurements]].
-Our generated results are pushed to a private GitHub repository (SCECcode/event-reports) that is directly read by the SCEC Event Page. You must be granted permission to view and contribute to this repository to continue publishing UCERF3-ETAS results for use in SCEC Event Pages.
+Our generated results are pushed to a private GitHub repository (SCECcode/ucerf3-etas-results) that is directly read by the SCEC Event Page. You must be granted permission to view and contribute to this repository to continue publishing UCERF3-ETAS results for use in SCEC Event Pages.
 ) Clone this repository to your home directory with the following command:
-<code>cd $HOME && git clone git@github.com:SCECcode/event-reports.git</code>
+<code>cd $HOME && git clone git@github.com:SCECcode/ucerf3-etas-results.git</code>
 ) Get scripts
@@ Line 89: / Line 89: @@
 ) Run ComCatReportPageGen
-The following example has the event-reports repository cloned in our home directory on Expanse. Execution updates the local repository, after which you can <code> git push</code> the changes upstream given sufficient permissions. Recall that such changes don't update an already generated SCEC Event page, in which case the page will have to be regenerated.
+The following example has the ucerf3-etas-results repository cloned in our home directory on Expanse. Execution updates the local repository, after which you can <code> git push</code> the changes upstream given sufficient permissions. Recall that such changes don't update an already generated SCEC Event page, in which case the page will have to be regenerated.
 <code>
 u3etas_jar_wrapper.sh org.opensha.commons.data.comcat.plot.ComcatReportPageGen --event-id ci41075584 \
---min-mag 0d --radius 50 --output-parent-dir /home1/10177/bhatthal/event-reports \
+--min-mag 0d --radius 50 --output-parent-dir /home1/10177/bhatthal/ucerf3-etas-results \
 --etas-dir $ETAS_SIM_DIR/frontera-comcat-malibu-m3.9-n14-s100000 \
---etas-output-dir /home1/10177/bhatthal/event-reports/ucerf3-etas
+--etas-output-dir /home1/10177/bhatthal/ucerf3-etas-results/ucerf3-etas
 </code>
@@ Line 105: / Line 105: @@
 If you are unable to identify the event-id, try passing with the shortened parameter and ensuring these is no space, i.e. `-eci41075584`.
-) Commit the changes in `event-reports` and push upstream to origin/master.
+) Commit the changes in `ucerf3-etas-results` and push upstream to origin/master.
 See the Git Troubleshooting section if you're unable to do this.
@@ Line 127: / Line 127: @@
 </code>
-In our example, we specify the absolute path to where we cloned the event-reports repository, as well as the absolute path to a UCERF3-ETAS results directory within the event-reports repository. Our results are written into two folders to allow us to filter by either date or Event ID.
+In our example, we specify the absolute path to where we cloned the ucerf3-etas-results repository, as well as the absolute path to a UCERF3-ETAS results directory within the ucerf3-etas-results repository. Our results are written into two folders to allow us to filter by either date or Event ID.
 If running on Expanse, copy any plots from scratch into your own account as we can't run in someone else's folder. You can create a tarball and copy the whole folder into your account. The same logic should apply to any other HPC system. Ensure you execute the script on an interactive node, not on the head node.

@@ Line 53: / Line 53: @@
 Our generated results are pushed to a private GitHub repository (SCECcode/event-reports) that is directly read by the SCEC Event Page. You must be granted permission to view and contribute to this repository to continue publishing UCERF3-ETAS results for use in SCEC Event Pages.
-. Clone this repository to your home directory with the following command:
+) Clone this repository to your home directory with the following command:
 <code>cd $HOME && git clone git@github.com:SCECcode/event-reports.git</code>
-. Get scripts
+) Get scripts
 We can't directly copy results into this repository. The data is prepared using the u3etas_jar_wrapper shell script. You should already have such scripts downloaded and made available to execute by adding to your PATH. If not, clone the repository.
@@ Line 63: / Line 63: @@
 <code>git clone https://github.com/opensha/ucerf3-etas-launcher.git</code>
-Ensure that you have selected the correct Event ID and directories. See the following section for an explanation of the parameters used.
+) Ensure that you have selected the correct Event ID and directories. See the following section for an explanation of the parameters used.
-. Set environment variables in bash config
+# Set environment variables in bash config
 * Ensure you're on an interactive node:
 * Update your bash config with:
@@ Line 80: / Line 80: @@
 </code>
-. Connect to an interactive node
+) Connect to an interactive node
 <code>srun --partition=debug  --pty --account=usc143 --nodes=1 --ntasks-per-node=4 --mem=16G -t 00:30:00 --wait=0 --export=ALL /bin/bash</code>
-. Ensure that you have sufficient memory for execution on this node.
+) Assuming you have reserved an interactive node with sufficient memory, ensure that you have sufficient memory for execution on this node.
-Set <code>ETAS_MEM_GB=32</code>. This doesn't have to be in your bash config, just execute directly. Adjust memory needed if you encounter an OutOfMemoryError during execution.
+Set <code>ETAS_MEM_GB=32</code>.
+* export ETAS_MEM_GB=32
 This doesn't have to be in your bash config, just execute directly. Adjust memory needed if you encounter an OutOfMemoryError during execution.
 The following example has the event-reports repository cloned in our home directory on Expanse. Execution updates the local repository, after which you can <code> git push</code> the changes upstream given sufficient permissions. Recall that such changes don't update an already generated SCEC Event page, in which case the page will have to be regenerated.
 <code>
@@ Line 106: / Line 105: @@
 If you are unable to identify the event-id, try passing with the shortened parameter and ensuring these is no space, i.e. `-eci41075584`.
-. Commit the changes in `event-reports` and push upstream to origin/master.
+) Commit the changes in `event-reports` and push upstream to origin/master.
 See the Git Troubleshooting section if you're unable to do this.

@@ Line 12: / Line 12: @@
 [[File:Malibu EQ.png|400px|thumb|Fig 2. SCEC Event Page for M4 earthquake near Malibu, CA]]
 [[File:UCERF3-ETAS Forecast in Event Page.png|400px|thumb|Fig 3. UCERF3-ETAS Forecast as seen on the Event Page]]
 == Publishing the UCERF3-ETAS Forecast ==
@@ Line 96: / Line 131: @@
 If running on Expanse, copy any plots from scratch into your own account as we can't run in someone else's folder. You can create a tarball and copy the whole folder into your account. The same logic should apply to any other HPC system. Ensure you execute the script on an interactive node, not on the head node.

← Older revision		Revision as of 18:56, 30 June 2025
Line 143:		Line 143:

	Handling of permissions for a Quakeworx GitHub account, structural changes for storing and reading results from the event-reports repository, and implementing a "Write to Event Page" boolean field on job submission is all feasible. Implementing a UI to retroactively change the selected forecast and trigger page regeneration would require further investigation into the capabilities of the Quakeworx framework and if there's an API for externally triggering the generator. These changes may improve the user experience and make publishing UCERF3-ETAS forecasts easier without requiring knowledge of a Linux terminal.		Handling of permissions for a Quakeworx GitHub account, structural changes for storing and reading results from the event-reports repository, and implementing a "Write to Event Page" boolean field on job submission is all feasible. Implementing a UI to retroactively change the selected forecast and trigger page regeneration would require further investigation into the capabilities of the Quakeworx framework and if there's an API for externally triggering the generator. These changes may improve the user experience and make publishing UCERF3-ETAS forecasts easier without requiring knowledge of a Linux terminal.
		+
		+
		+	== Quakeworx ==
		+	Results can be published even when generated on Quakeworx, not just directly via the command-line.
		+	Results are stored inside the Quakeworx development (qwxdev) scratch directory, but each user has a unique ID where their jobs are written to. Below is a list of known Drupaluid IDs for users who frequently run UCERF3-ETAS on Quakeworx.
		+	* Phil Maechling: 6
		+	* Fabio Silva: 7
		+	* Akash Bhatthal: 20
		+
		+	For example, a job Phil ran on Quakeworx labelled "DeepSprings_EQ" would be found at <code>/expanse/lustre/scratch/qwxdev/temp_project/qwx1/users/drupaluid_6/jobs/DeepSprings_EQ/</code>.
		+
		+	In order to run the ComcatReportPageGen, you should copy this event from scratch into your own home directory. Here you can make changes to the config.json configuration as necessary and execute the generator (See step 6) with an updated etas-dir.