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

D3ploy can't divide the production of power into different types of reactors. #255

Closed robfairh closed 5 years ago

robfairh commented 5 years ago

When the demand of power should be met by two types of reactors, for ex: 40% by MOX lwr's and 60% FR's, d3ploy won't do it. It will deploy reactors to meet the demand equation without considering the percentages. There isn't a way to define those percentages or to limit the number of facilities deployed.

In d3ploy the definition of two types of reactors is like this: image

A way to solve this would be using the preferences and modify the lifetime of the previous reactors accordingly: image

image

This solution deploys first fr's and then mox's. D3ploy should be able to deploy both reactors at the same time and the user should be able to define the percentages of power that d3ploy should meet.

gwenchee commented 5 years ago

@robfairh Could you describe how this sharing capability works here? With respect to constraint, preferences etc. Like what happens first?

robfairh commented 5 years ago

It checks first if there are preferences greater than 0. If there are, it checks if they are equal. If they are different, then it deploys the one with the highest preference. If they are equal, it checks if they have a sharing preference. If it does, then it deploys based on that. If it doesn't it deploys the min number of facilities.

robfairh commented 5 years ago

closed by #279