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

"from reported to now" doesn't work in Tracker #2210

Open
BrianCollinss opened this issue Jun 27, 2023 · 10 comments
Open

"from reported to now" doesn't work in Tracker #2210

BrianCollinss opened this issue Jun 27, 2023 · 10 comments

Comments

@BrianCollinss
Copy link
Member

I used to be able to get the average of a variable from last day reported until now:

average of mint on end_of_day from reported to now as meanTMin

Now, it doesn't work. Am I doing something wrong here?

@peter-devoil
Copy link
Collaborator

That used to work for me too. Have you got reporting events that trigger it?

sum of runoff on end_of_day from reported to now as YearlyRunoff

@BrianCollinss
Copy link
Member Author

Hi Peter. I do have reporting events triggered via a manager script.

@peter-devoil
Copy link
Collaborator

Perhaps the log component might help show you what events are being published, and what variables are being captured. It's not a scope (paddock vs global) issue?

@BrianCollinss
Copy link
Member Author

BrianCollinss commented Jun 28, 2023

My Tracker is under the parent / Simulations folder now. Here is my summary file.

Simulations.log

@peter-devoil
Copy link
Collaborator

I think the tracker should be a sibling of the report module. IIRC, "events propogate down the tree", so a clock event makes its way down to all leaves; but a harvesting event sent from within a paddock wont leave that paddock. The "diagnostic log file" has the nitty gritty

@BrianCollinss
Copy link
Member Author

I moved the tracker below the report, but it didn't fix it. I tried to make it a child of the report, but it wasn't possible.

@peter-devoil
Copy link
Collaborator

The log component is in the management toolbox, iirc. You can get an idea of "normal sequence of events" from one of the example simulations by heavy use of the search/grep button.. Then see what messages are being exchanged in yours to identify misbehaviour.

@BrianCollinss
Copy link
Member Author

BrianCollinss commented Jun 29, 2023

It seems those variables were printed in the output files when I used our latest Singularity on HPC. But I get ? when I run locally (r4220).

Does this log file help? BTW, I use seasonalReport.Publish("do_output") to trigger a report event.

logfile.log

@peter-devoil
Copy link
Collaborator

Another reason why bootlegs are bad news

If you're seeing a single "?", then it means it never saw a "reported" event before.

If you're seeing each line as a "?" then there's no "end_of_day" event going past

"end_of_day" was a pseudonym for "post", or the other way around. Try using "post" and see.

P

@BrianCollinss
Copy link
Member Author

Thanks Peter. None of the solutions worked. Strange thing is that the simulations run on the HPC do have values for tracker outputs.

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

No branches or pull requests

2 participants