Comments (10)
can you show me the input xml for the d3ploy institution section of the input file?
from d3ploy.
This is it for both input files:
from d3ploy.
The input files are here:
https://github.com/robfairh/transition-scenarios/tree/experimental3/input/eg01-eg29
- eg01-eg29-flatpower-d3ploy6.xml is the one that doesn't display anything in the table
- eg01-eg29-flatpower-d3ploy7.xml displays the table
from d3ploy.
Itβs not obvious to me what is the issue. Maybe you need to do some debugging in the source code?
from d3ploy.
Let's go into the code and do some debugging @robfairh
from d3ploy.
I run this file
And even though it doesn't use d3ploy, it doesn't have the tables timeserieddemandlwrpu and timeseriesdemandmoxpu:
So @FlanFlanagan was right, the issue is something in cycamore and the way the tables are recorded.
Even though having those tables makes life easier, I am not sure they are needed by d3ploy to deploy the right thing. This continues on my next comment.
from d3ploy.
To make things simpler I made the following inputs:
-
nond3ploy-simple.xml:
https://github.com/robfairh/transition-scenarios/blob/experimental6/input/eg01-eg29/nond3ploy-simple.xml -
d3ploy-simple1.xml
https://github.com/robfairh/transition-scenarios/blob/experimental6/input/eg01-eg29/d3ploy-simple1.xml -
d3ploy-simple2.xml
https://github.com/robfairh/transition-scenarios/blob/experimental6/input/eg01-eg29/d3ploy-simple1.xml -
d3ploy-simple3.xml
https://github.com/robfairh/transition-scenarios/blob/experimental6/input/eg01-eg29/d3ploy-simple3.xml
1)Doesn't use d3ploy, it's just the nond3ploy version, I deployed everything manually.
2)Not very important, but it just deploys sinks to see that d3ploy works with the input.
These two work fine.
3)the mixer is deployed using d3ploy. The table timeseriescalc_capacitylwrpu is 0 at all times. This causes the simulation to deploy new mixing facilities at all times. For this case, the mixer has two inputs for Pu lwrpu and frpu.
4)the mixer is still deployed using d3ploy. This time, the mixer has only one input for Pu, lwrpu. This time calc_capacitylwrpu is 3000. And it deploys only one mixer. Of course this transition doesn't work because it won't use frpu, but the case helps to show what d3ploy is doing.
from d3ploy.
It works well when I used the feature "installed_capacity" (thanks, @gwenchee),
now the issue could be closed when the predicted capacity feature works as well.
from d3ploy.
Using installed capacity still has issues with the full input:
The capacity of the frmixer is 13e3 and the capacity of the moxmixer is 8e3. The supply of Pu is 20.8e3 then it deploys 1 frmixe and 1 moxmixer. The capacity should be 21e3, but the table shows just 8e3. Then on the next time step where there is a supply of Pu, it deploys 2 more moxmixer, the table shows a capacity for lwrpu of 24e3. The table is just recording the capacity of one of the prototypes (moxmixer) deployed by d3ploy. Both frmixer and moxmixer are supply driven deployed by the same commodity: lwrpu.
from d3ploy.
In the beginning it wasn't clear what the issue was. After looking into it, we found that this issue can be decoupled into 3 smaller issues. This issue is closed, and the 3 issues are open. These are #270, #273, #274.
from d3ploy.
Related Issues (20)
- combine demand driven inst and supply driven inst HOT 3
- D3ploy can't divide the production of power into different types of reactors. HOT 3
- pytest - ImportError: cannot import name 'main' HOT 21
- Buffer Type change HOT 1
- D3ploy is not running FFT properly on numpy 1.16.4 HOT 10
- Add function in tester.py to obtain cumulative difference between demand and supply HOT 1
- Mixer doesn't record the demand of all the input commodities. HOT 1
- constraint commodity capability bug HOT 1
- d3ploy fails to record the capacity of mixers deployed with multiple inputs HOT 2
- D3ploy fails to record the capacity of mixers when they are deployed using the same commodity. HOT 1
- Buffer malfunctioning HOT 6
- D3ploy Doesn't Work HOT 13
- update config.yml file to include all the new tests HOT 3
- calc_demand takes the values of the demand_eq HOT 2
- Some of the methods don't actually use the back_steps HOT 1
- Some of the prediction methods don't have the capability to look forward. HOT 3
- Installed cap should't be used with the back end HOT 3
- Installation Issue HOT 16
- Update Documentation HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. πππ
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google β€οΈ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from d3ploy.