-
Notifications
You must be signed in to change notification settings - Fork 19
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
Agents Metric #27
Agents Metric #27
Conversation
If the exit time is not specified in the original db and the agent was never scheduled for decommissioning, what is put in the ExitTime column here? - I'm not familiar enough with pandas to know by just looking at the code. The value should be maintained as "NULL", -1, or some other such non-normal value because no exit time is semantically different to cyclus than a future or end of sim exit time - particularly w.r.t. restart/branching. |
I'm getting errors when I run nosetests that relate to the tests not being able to import cyclus |
What directory are you in? |
cymetric/tests when I run nosetests |
hmmm can you post the error please? |
Did you re-install? |
I did reinstall cymetric (oh so cleanly) Here are the errors I get:
|
It puts in the simulation duration from the Info table. I think that this is better than what cyclist does, which is to add the simulation duration to the EnterTime. For example, if the simulation duration is 100, and the enter time for an agent is 10, then cymetric will use 100 as the exit time and cyclist will use 110.
It is maintained in the appropriate tables (AgentEnter, AgentExit, DecomSched, etc). The Agents table, like in cyclist is present for analysis and visualization, not for restart. It is there to be able to figure out in a consistent manner when agents are alive. Calling the last column AgentExit is probably a misnomer, but I was trying to match the cyclist table. It is hard to create a plot when the upper value of the time range is NaN :). I hope that this explains it. |
@opotowsky this seems to be a Python 2 issue, or at least the first one is. |
I clean installed both cyclus and cymetric and am still getting the import errors. Should I worry about the first error? |
I'll try to get a fix in for these later today. |
thanks so much! |
@opotowsky can you try the docstring fix I have just pushed up? |
Thanks for the quick fix, but now I get this!
|
Ok! Try this. |
Alright, I have now updated this to actually work on Python 2. Sorry it took me a while. I had to install Python 2, etc :) |
On my bat-loving, hdf5-hating computer now so those are the only test failures. Excitedly merging, thanks @scopatz! |
This implements an "Agents" table and metric that matches the schema and semantics of a table by the same name that is generated by cyclist. It also addresses a deficiency in the cyclist table where the ExitTime could be greater than the duration. Some fixes, ui improvements, and interfaces have been updated along the way.