search

arfc / d3ploy

A collection of Cyclus manager archetypes for demand driven deployment
BSD 3-Clause "New" or "Revised" License
4 stars 11 forks source link

give d3ploy the capability of an initial condition #252

Closed gwenchee closed 5 years ago

gwenchee commented 5 years ago

The issue can be closed when d3ploy has the capability of having an inital condition of facilities in the institution.

FlanFlanagan commented 5 years ago

Doesn't it already have this capability? Or are you saying initial condition and it deploys to meet it?

gwenchee commented 5 years ago

I'm pretty sure it does not have capability of having an initial number of facilities in the institution before it deploys to meet a demand that is set?

FlanFlanagan commented 5 years ago

I mean, you could manually set the number of facilities in the initial facility list?

FlanFlanagan commented 5 years ago

Alternatively you can probably set a variable to have to call deployments during agent entry, but I've never done that. So I'm not sure it'll work.

gwenchee commented 5 years ago

The reason for the initial condition is so that the institution is aware of all the installed capacity it has. Because we want to implement the option of using installed capacity to govern the deployment of facilities. d3ploy doesn't know the installed capacity of all the facilities outside of it if we use initial facility list or deployinst to deploy the facilities.

gwenchee commented 5 years ago

What do you mean by set a variable to have to call deployments during agent entry? @FlanFlanagan

FlanFlanagan commented 5 years ago

Well, it might be possible to say, start with 1000 POWER. Then during agent entry, call the deployment solver for that difference and have them deploy at timestep 0.

gwenchee commented 5 years ago

What do you mean by during agent entry? Isn’t that a table name? I was thinking of just scheduling a build at the first time step, but that makes them not initial facilities.

On Thu, May 2, 2019 at 5:58 PM FlanFlanagan notifications@github.com wrote:

Well, it might be possible to say, start with 1000 POWER. Then during agent entry, call the deployment solver for that difference and have them deploy at timestep 0.

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/arfc/d3ploy/issues/252#issuecomment-488861823, or mute the thread https://github.com/notifications/unsubscribe-auth/AHAJG7BJUSN7YKZ5QDYAUF3PTNW23ANCNFSM4HJYIDHA .

-- Gwendolyn J. Chee Master's Student Department of Nuclear, Plasma and Radiological Engineering University of Illinois at Urbana-Champaign Email: gchee2@illinois.edu

FlanFlanagan commented 5 years ago

On the enter_notify() function.

FlanFlanagan commented 5 years ago

Sorry, I used poor terminology.

gwenchee commented 5 years ago

Hm, I actually tried doing that but it didn’t let me schedule a build in enternotify

On Thu, May 2, 2019 at 8:50 PM FlanFlanagan notifications@github.com wrote:

Sorry, I used poor terminology.

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/arfc/d3ploy/issues/252#issuecomment-488889767, or mute the thread https://github.com/notifications/unsubscribe-auth/AHAJG7ABOABDCWB3ADEFKBDPTOK43ANCNFSM4HJYIDHA .

-- Gwendolyn J. Chee Master's Student Department of Nuclear, Plasma and Radiological Engineering University of Illinois at Urbana-Champaign Email: gchee2@illinois.edu

gwenchee commented 5 years ago

This is done by adding an initialfacilitylist to the d3ploy institution. This is done in https://github.com/arfc/d3ploy/pull/259