-
Notifications
You must be signed in to change notification settings - Fork 102
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
plotting resids with PDC #164
Comments
I think we do need to get better at handling conflicts in general. But instead of dropping, what about having them washed out or otherwise colored differently or at least have that option? There is a more advanced PDC detection routine in helpers now so we could potentially just call that under the hood in the plotting so that we dont have an external file dependency (that may change in the future!). Just my thoughts. |
@mnfienen - any interest in this option still? |
Yeah - I do think this might be useful (although I've been going rogue with 1to1 plots lately). Maybe could have two options for Also, for some recent work, found it valuable to plot 1to1 with error bars in both obs and modeled like the attached. Maybe can fold that into pyemu? |
Those plots look awesome! We could also just have variants on the 1-to-1 plots since all of us GW modelers are so obsessed with it - like a |
@mnfienen - any movement on this? |
@jtwhite79 nope lol. I can try and revisit though! |
@mnfienen, happy for me to move this to discussions? Might be good to revisit when whoever has the time? |
In cases where
++ies_drop_conflicts
is True, it would be nice to eliminate those dropped obs (especially if they are really really bad!) from plots like 1to1 plots. A simple flag could be supplied topst.plot(kind='1to1', drop_pdc=True)
for example, that reads the csv file with PDC-dropped obs and just removes them before plotting.I can implement, but wanted to see if anyone has objections or other ideas of how to deal.
The text was updated successfully, but these errors were encountered: