SCEC Event Page Troubleshooting - Revision history

Bhatthal at 22:35, 2 April 2026

2026-04-02T22:35:20Z

Bhatthal: /* Apr 2 2026 - Failure to generate "M4.6 - 1 km SE of Boulder Creek, CA 04/02/2026 (nc75337442)" (Resolved) */

2026-04-02T21:06:11Z

Apr 2 2026 - Failure to generate "M4.6 - 1 km SE of Boulder Creek, CA 04/02/2026 (nc75337442)" (Resolved)

Bhatthal at 20:57, 2 April 2026

2026-04-02T20:57:33Z

Bhatthal: Create entry for bug report on apr 2 2026

2026-04-02T20:54:45Z

Create entry for bug report on apr 2 2026

Bhatthal at 22:36, 16 November 2025

2025-11-16T22:36:05Z

Bhatthal at 21:53, 16 November 2025

2025-11-16T21:53:16Z

Bhatthal: Create troubleshooting entry

2025-11-16T18:18:58Z

Create troubleshooting entry

New page

This page outlines all encountered bugs with the process of generating SCEC Event Pages. Each bug should have a header with a succinct summary and the date it was first encountered. Bugs that have been resolved will have "'''(Resolved)'''" appended to its header.

== Nov 4 2025 - Failure to generate "M3.1 - 10km NNE of Yucaipa, CA 10/23/2025 (ci41113519)" '''(Resolved)''' ==
Failed to generate a SCEC Event Page for the “M3.1 - 10km NNE of Yucaipa, CA 10/23/2025 (ci41113519)” event on the event generation page at https://central.scec.org/earthquakes/eventpage/generate.
Ambiguous error, “error generating page” and simply “error” using the “Enter USGS ID to Generate Page” and “Recent Earthquakes” Generate buttons.
Bug is only encountered with this specific event. Able to generate an event page for 10/23/2205 Woodside, but not 10/23/2025 Yucaipa.

[[Image:Yucaipa-error-msg.png|450px]]
Chrome Developer Tools allow for analysis of the JSON error message.
[[Image:Yucaipa-err-json-response.png|450px]]

A match for the error detail is found in the <code>earthquake_event_page.php</code> script at function <code>scec_earthquake_event_page_generate($event_id)</code>.
This error is returned due to a non-zero return value from the execution of <code>update_eq_event_report.sh</code>.

'''TODO: Finish this section'''

== Related Entries ==
* [[Publishing_UCERF3-ETAS_Event_Reports]]

← Older revision		Revision as of 22:35, 2 April 2026
Line 12:		Line 12:

	After testing locally with Docker eclipse-temurin:17-jdk using the OpenSHA fat jar on opensha/opensha:master at commit c2e5c3da8fa74d9cc46b73d9f0d6d9671b34285c, we are able to generate the page successfully. The fat jar in repository opensha-event-reports is updated accordingly and changes are pulled on the server for production.		After testing locally with Docker eclipse-temurin:17-jdk using the OpenSHA fat jar on opensha/opensha:master at commit c2e5c3da8fa74d9cc46b73d9f0d6d9671b34285c, we are able to generate the page successfully. The fat jar in repository opensha-event-reports is updated accordingly and changes are pulled on the server for production.
		+
		+	[[Image:boulder-creek-generated-20260402.png\|500px\|frameless]]
		+
		+	'''Fig 2. Boulder Creek event page generated successfully'''
		+

	== Nov 4 2025 - Failure to generate "M3.1 - 10km NNE of Yucaipa, CA 10/23/2025 (ci41113519)" '''(Resolved)''' ==		== Nov 4 2025 - Failure to generate "M3.1 - 10km NNE of Yucaipa, CA 10/23/2025 (ci41113519)" '''(Resolved)''' ==

← Older revision		Revision as of 21:06, 2 April 2026
Line 12:		Line 12:

	After testing locally with Docker eclipse-temurin:17-jdk using the OpenSHA fat jar on opensha/opensha:master at commit c2e5c3da8fa74d9cc46b73d9f0d6d9671b34285c, we are able to generate the page successfully. The fat jar in repository opensha-event-reports is updated accordingly and changes are pulled on the server for production.		After testing locally with Docker eclipse-temurin:17-jdk using the OpenSHA fat jar on opensha/opensha:master at commit c2e5c3da8fa74d9cc46b73d9f0d6d9671b34285c, we are able to generate the page successfully. The fat jar in repository opensha-event-reports is updated accordingly and changes are pulled on the server for production.
−
−	~~TODO: Test if the prod deployment generates the event page successfully.~~
−

	== Nov 4 2025 - Failure to generate "M3.1 - 10km NNE of Yucaipa, CA 10/23/2025 (ci41113519)" '''(Resolved)''' ==		== Nov 4 2025 - Failure to generate "M3.1 - 10km NNE of Yucaipa, CA 10/23/2025 (ci41113519)" '''(Resolved)''' ==

@@ Line 11: / Line 11: @@
 The bug was identified in the ComcatReportPageGen tool. Merging pager images fails due to mismatched image widths. Updating the bounds resolves the bug. (See [https://github.com/opensha/opensha/pull/223 #223] for details)
-TODO: After testing locally with Docker eclipse-temurin:17-jdk using the OpenSHA fat jar on master at commit c2e5c3da8fa74d9cc46b73d9f0d6d9671b34285c, we are able to generate the page successfully. The fat jar in repository opensha-event-reports is updated accordingly and changes are pulled on the server for production.
+After testing locally with Docker eclipse-temurin:17-jdk using the OpenSHA fat jar on opensha/opensha:master at commit c2e5c3da8fa74d9cc46b73d9f0d6d9671b34285c, we are able to generate the page successfully. The fat jar in repository opensha-event-reports is updated accordingly and changes are pulled on the server for production.
 TODO: Test if the prod deployment generates the event page successfully.

← Older revision		Revision as of 20:54, 2 April 2026
Line 1:		Line 1:
	This page outlines all encountered bugs with the process of generating SCEC Event Pages. Each bug should have a header with a succinct summary and the date it was first encountered. Bugs that have been resolved will have "'''(Resolved)'''" appended to its header.		This page outlines all encountered bugs with the process of generating SCEC Event Pages. Each bug should have a header with a succinct summary and the date it was first encountered. Bugs that have been resolved will have "'''(Resolved)'''" appended to its header.
		+
		+	== Apr 2 2026 - Failure to generate "M4.6 - 1 km SE of Boulder Creek, CA 04/02/2026 (nc75337442)" '''(Resolved)'''==
		+	Failed to generate a SCEC Event Page for the “M4.6 - 1 km SE of Boulder Creek, CA 04/02/2026 (nc75337442)” event on the event generation page at https://central.scec.org/earthquakes/eventpage/generate.
		+
		+	[[Image:error-generating-m4.6-boulder-creek-20260402.png\|500px\|frameless]]
		+
		+	'''Fig 1. Error generating Boulder Creek event'''
		+
		+
		+	The bug was identified in the ComcatReportPageGen tool. Merging pager images fails due to mismatched image widths. Updating the bounds resolves the bug. (See [https://github.com/opensha/opensha/pull/223 #223] for details)
		+
		+	TODO: After testing locally with Docker eclipse-temurin:17-jdk using the OpenSHA fat jar on master at commit c2e5c3da8fa74d9cc46b73d9f0d6d9671b34285c, we are able to generate the page successfully. The fat jar in repository opensha-event-reports is updated accordingly and changes are pulled on the server for production.
		+
		+	TODO: Test if the prod deployment generates the event page successfully.
		+

	== Nov 4 2025 - Failure to generate "M3.1 - 10km NNE of Yucaipa, CA 10/23/2025 (ci41113519)" '''(Resolved)''' ==		== Nov 4 2025 - Failure to generate "M3.1 - 10km NNE of Yucaipa, CA 10/23/2025 (ci41113519)" '''(Resolved)''' ==

@@ Line 6: / Line 6: @@
 Bug is only encountered with this specific event. Able to generate an event page for 10/23/2205 Woodside, but not 10/23/2025 Yucaipa.
-[[Image:Yucaipa-error-msg.png|450px|thumb|Fig 1. Error generating Yucaipa event]]
+[[Image:Yucaipa-error-msg.png|500px|frameless]]
 Chrome Developer Tools allow for analysis of the JSON error message. (See Fig. 2)
-[[Image:Yucaipa-err-json-response.png|450px|thumb|Fig 2. Resolve ambiguous error message with Chrome Developer Tools]]
+[[Image:Yucaipa-err-json-response.png|500px|frameless]]
 A match for the error detail (See Fig 3.) is found in the <code>earthquake_event_page.php</code> script at function <code>scec_earthquake_event_page_generate($event_id)</code>.
-[[Image:Yucaipa-eq-event-page-php-snippet.png|450px|thumb|Fig 3. Error detail match found in code]]
+[[Image:Yucaipa-eq-event-page-php-snippet.png|500px|frameless]]
 This error is returned due to a non-zero return value from the execution of <code>update_eq_event_report.sh</code>. Upon analysis of Docker logs we see this failure is in the Docker execution of <code>generate_report.sh</code> (See Fig. 4)
-[[Image:Yucaipa-update-eq-event-report-sh-snippet.png|450px|thumb|Fig 4. update_eq_event_report.sh invokes Docker Java 8 for generate_report.sh]]
+[[Image:Yucaipa-update-eq-event-report-sh-snippet.png|500px|frameless]]
 <code>generate_report.sh</code> invokes the Java OpenSHA <code>ComcatReportPageGen</code> CLT with appropriate parameters.
 See logs below:
 <code>
-Array
+Array(
      [0] => cd /data/scectmp
      [1] => run docker
@@ Line 63: / Line 75: @@
      [35] =>    at org.opensha.commons.data.comcat.plot.ComcatReportPageGen.generateReport(ComcatReportPageGen.java:384)
      [36] =>   at org.opensha.commons.data.comcat.plot.ComcatReportPageGen.main(ComcatReportPageGen.java:1418)
-     [37] => quitting with error
+     [37] => quitting with error)</code>
 Here is a snippet of <code>ComcatDataPlotter</code>, where the error is thrown. (See Fig. 5)
-[[Image:Comcatdataplotter-fail-snippet.png|450px|thumb|Fig 5. Failed Precondition in ComcatDataPlotter]]
+[[Image:Comcatdataplotter-fail-snippet.png|500px|frameless]]
 It’s resolving NaN, because minDataMag is set to infinity. We failed to find any of mainshock.getMag, foreshocksFunc.getMinY, or aftershocksFunc.getMinY
@@ Line 87: / Line 100: @@
 This code will be merged into the OpenSHA codebase with a PR after review. Changes incurred at merge will require a new Jar to be built and deployed to the Central SCEC Server.
-[[Image:Yucapia-comcatdataplotter-fix.png|450px|thumb|Fig 6. Add NaN checks in ComcatDataPlotter]]
+[[Image:Yucapia-comcatdataplotter-fix.png|500px|frameless]]
 After we deployed the new Jar, we updated the docker image invoked in <code>update_eq_event_report.sh</code> from <code>openjdk:8</code> to <code>eclipse-temurin:11-jdk</code>.

@@ Line 3: / Line 3: @@
 == Nov 4 2025 - Failure to generate "M3.1 - 10km NNE of Yucaipa, CA 10/23/2025 (ci41113519)" '''(Resolved)''' ==
 Failed to generate a SCEC Event Page for the “M3.1 - 10km NNE of Yucaipa, CA 10/23/2025 (ci41113519)” event on the event generation page at https://central.scec.org/earthquakes/eventpage/generate.
-Ambiguous error, “error generating page” and simply “error” using the “Enter USGS ID to Generate Page” and “Recent Earthquakes” Generate buttons.
+Ambiguous error, “error generating page” and simply “error” using the “Enter USGS ID to Generate Page” and “Recent Earthquakes” Generate buttons. (See Fig 1.)
 Bug is only encountered with this specific event. Able to generate an event page for 10/23/2205 Woodside, but not 10/23/2025 Yucaipa.
-[[Image:Yucaipa-error-msg.png|450px]]
+[[Image:Yucaipa-error-msg.png|450px|thumb|Fig 1. Error generating Yucaipa event]]
-A match for the error detail is found in the <code>earthquake_event_page.php</code> script at function <code>scec_earthquake_event_page_generate($event_id)</code>.
+Chrome Developer Tools allow for analysis of the JSON error message. (See Fig. 2)
 This error is returned due to a non-zero return value from the execution of <code>update_eq_event_report.sh</code>.
 == Related Entries ==
 * [[Publishing_UCERF3-ETAS_Event_Reports]]