-
Notifications
You must be signed in to change notification settings - Fork 3
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
Forcing factors don't change future forcing, only historical #78
Comments
Just to clarify, I think the problem is actually that the aerosol and volcanic forcing scaling factors don't change forcing in the UI at all (neither historical nor future). They DO change temperature, so they are having an effect on the model, but just not showing up in the plots of forcing. |
Hi @bconeill88, an update on this - you're correct that changing the RFs do impact the model, but are not being updated in the individual forcing outputs. The hector dev team is aware of this bug (JGCRI/hector#743 and JGCRI/hector#745) and are working to fix it in their next release. For hectorUI, our temporary solution would be to remove the graphing capabilities for those RFs outputs (aerosols and volcanic forcing). @kdorheim and I are curious your thoughts on the priority of fixing this? Since it would constitute a major version change to the model, the release may not happen until next year otherwise. |
Hi Stephanie, thanks for the update, glad to hear you are working on this.
Since it is not a problem with how the model itself is working, I don't
think it is super high priority. The temporary fix and the plan to include
a permanent one in the next major release sounds reasonable to me.
…On Tue, Aug 6, 2024 at 11:51 AM Stephanie Pennington < ***@***.***> wrote:
Hi @bconeill88 <https://github.com/bconeill88>, an update on this -
you're correct that changing the RFs do impact the model, but are not being
updated in the individual forcing outputs. The hector dev team is aware of
this bug (JGCRI/hector#743 <JGCRI/hector#743>
and JGCRI/hector#745 <JGCRI/hector#745>) and are
working to fix it in their next release.
For hectorUI, our temporary solution would be to remove the graphing
capabilities for those RFs outputs (aerosols and volcanic forcing).
@kdorheim <https://github.com/kdorheim> and I are curious your thoughts
on the priority of fixing this? Since it would constitute a major version
change to the model, the release may not happen until next year otherwise.
—
Reply to this email directly, view it on GitHub
<#78 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/BJACWAI6UI6KEMZXEFOWXTTZQDWIDAVCNFSM6AAAAABI5GOIGSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZRGYYTMOJQGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Submitter: @stephpenn1 on behalf HectorUI Tutorial feedback
Describe the bug
Aerosol forcing factor and volcanic forcing factor does not visually seem to affect future forcing
To Reproduce
Steps to reproduce the behavior:
From user:
The text was updated successfully, but these errors were encountered: