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

Mean loss curve computation updated #1145

Merged
merged 2 commits into from Apr 19, 2013
Merged

Mean loss curve computation updated #1145

merged 2 commits into from Apr 19, 2013

Conversation

matley
Copy link
Contributor

@matley matley commented Apr 19, 2013

with EnginePerformanceMonitor(
'populating gmf_agg', self.job.id, tracing=True):
post_processing.populate_gmf_agg(self.hc)

if self.hc.hazard_curves_from_gmfs:
Copy link
Contributor

Choose a reason for hiding this comment

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

Was this moved in core.py just for better visibility?

Copy link
Contributor

Choose a reason for hiding this comment

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

Uhm, actually this allows to distinguish the time spent from generating the hazard curves from the aggregation time, so I like it.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

No, as explained in the launchpad issue, currently we are re-arranging gmf only if hazard curves are computed. As this is optional, this fixes a bug as we always want the gmf_agg to be populated

@micheles
Copy link
Contributor

LGTM

matley added a commit that referenced this pull request Apr 19, 2013
Mean loss curve computation updated
@matley matley merged commit 22d5f13 into gem:master Apr 19, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants