ARISTOTLE: use the preferred shakemap version if more than one is available
#10120
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… case of ties, get the one with the most recent updateTime
ptormene
changed the title
preferred shakemap version if more than one is available
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I implemented a logic that follows the description of
preferredWeightin https://earthquake.usgs.gov/data/comcat/#product_preferredWeight, i.e.:Relative weight of product. When multiple products of the same type are associated to an event, one product of each type is considered "most preferred" This is defined as the product of that type with the largest preferredWeight, and when two products have equal preferredWeight the most recent updateTime is more preferred.I also tried to collect some information about the shakemap that is used (see bd96e94), but it is not so straightforward to propagate such information in order to make it visible in the outputs page, so I am postponing that work to a separate PR.