Skip to content
New issue

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

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add placeholder error messages where currently there are none #127

Merged
merged 79 commits into from
Jan 19, 2022

Conversation

kilicomu
Copy link
Contributor

A quick pass with a shell script to attempt to replace empty error messages with at least somewhat meaningful messages.

The LOC variable is not defined in various subroutines, and requires adding to those routines to progress.

Closes #126

@lizziel
Copy link
Contributor

lizziel commented Jan 13, 2022

@kilicomu, thanks for taking this!!

@kilicomu
Copy link
Contributor Author

That's the calls to HCO_ENTER tidied up. I've noticed that in some places LOC is declared but not defined - I'll go through and try to catch those.

@kilicomu kilicomu changed the title Initial attempt at adding placeholder error messages Add placeholder error messages where currently there are none Jan 17, 2022
@lizziel lizziel linked an issue Jan 18, 2022 that may be closed by this pull request
@lizziel
Copy link
Contributor

lizziel commented Jan 18, 2022

Heads up our 13.4.0 code freeze date is this coming Friday. Any chance this could be ready by then? No pressure. It could also go into a 13.4.Z since it will not change benchmark output.

@kilicomu
Copy link
Contributor Author

Sure thing - I'll try do it today and mark it ready for you to review.

@kilicomu kilicomu marked this pull request as ready for review January 19, 2022 16:49
@yantosca yantosca self-assigned this Jan 19, 2022
@yantosca yantosca added the category: Feature Request New feature or request label Jan 19, 2022
@yantosca yantosca added this to the 3.4.0 milestone Jan 19, 2022
@kilicomu
Copy link
Contributor Author

Okay, I think this is ready for you guys to take a look at.

I should say that I think there's more to be done in cleaning up the HEMCO error handling, as there is a lot of duplication of messages and inconsistencies throughout. Also, this PR doesn't add any meaningful messages where it adds new error messages, so those will need to be added at some point.

I think we all know about the above problems though, so hopefully this is a step in the right direction and we can talk about a strategy for further improving the error handling at the next software engineering meeting.

Copy link
Contributor

@yantosca yantosca left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a great update! I don't see any issues with it so we can go ahead and update it. I can get this into HEMCO 3.4.0 ASAP.

@kilicomu
Copy link
Contributor Author

Cool - drop me a line if anything turns awry with this and I'll pick it up!

@yantosca yantosca merged commit 06dfdc8 into geoschem:dev Jan 19, 2022
@yantosca
Copy link
Contributor

Will run integration tests so we'll know if there are issues. Thanks @kilicomu!

@yantosca
Copy link
Contributor

GEOS-Chem integration tests all passed, except for TOMAS40 (as explained in geoschem/geos-chem#1101)

gc_4x5_fullchem_TOMAS40_merra2_47L...............Execute Simulation.....FAIL

Summary of test results:
------------------------------------------------------------------------------
Execution tests passed: 47
Execution tests failed: 1
Execution tests not yet completed: 0

GCHP integration tests all passed:

==============================================================================
GCHP: Execution Test Results

Number of execution tests: 3
==============================================================================
 
Execution tests:
------------------------------------------------------------------------------
gchp_fullchem_benchmark_merra2_c48...............Execute Simulation.....PASS
gchp_fullchem_standard_merra2_c24................Execute Simulation.....PASS
gchp_TransportTracers_geosfp_c24.................Execute Simulation.....PASS
 
Summary of execution test results:
------------------------------------------------------------------------------
Execution tests passed:        3
Execution tests failed:        0
Execution tests not completed: 0

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%  All execution tests passed!  %%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category: Feature Request New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[FEATURE REQUEST] Call HCO_ERROR whenever RC is not HCO_SUCCESS
3 participants