Reactor planner version 2

    Quote from Talonius


    - A finer heat bar would be dobable


    Thanks!


    The heating and cooling happens in granular 1 second intervals. For heat generated as an exact factor of cooling, that works, but when they aren't the shorter the timing the more that granularity is apparent. I'll give an example of what I mean.


    http://www.talonfiremage.pwp.b…q=1k101010015015111r11r10 176 heat, 66 cooling 200 active eu/t 3.33 energy efficiency.
    Minimum timer 1 sec generating / 2 sec cooling. 66.667 eff eu/t (because 22 cooling is wasted every 3 seconds using this minimum timer)
    Maximum timer 33min 15 sec generating / 55min 41 sec cooling 74.8 eff eu/t This should actually be shortened to 55min 40s, waiting that last second for it to finish cooling means the first second it is generating wastes 66 cooling, effective eu/t is 75
    8.133 eu/t is gained by going from the minimum complexity timer to the maximum. 80% of that is 6.506. What is the minimum timer that gets 6.506 better then the simplest possible timer, and no more than 1.627 worse than the most complex timer possible?
    2sec on / 4 sec off is 66.667, same as minimum.
    3sec on / 5sec off gets 75, same as maximum. This is the minimum complex timer that gets at least 80% of the difference. It happens to get 100% of the difference, being perfectly equivalent to the best timer.


    With a linearly increasing timer complexity, for people like me who don't use redpower/ computer controller mods, this simplifies the construction of the timer by a factor of 665. Going with the simplest one is a wise choice if not a lot of cooling gets wasted, but in this case a timer less than 3x as complex gets >10% output boost. Being able to contrast simplest, most complex, and most of the way toward best output at a glance lets you make decisions about what kind of timer to construct. That was my thought at least. I don't know how many mad scientists make mark IVs without redpower or other smart controller mods. I may be the only person that uses that feature.




    Quote from Talonius


    - I'm unsure what you mean with the last idea, the planner already displays the amount of 'top-up' lava needed for pre-heated designs that cooldown over time even when generating. (In the Breeder info panel)


    Instead of the user using a slider to create a target starting heat, that slider becomes a target for target heat during operation. With a perfect breeder, starting heat is operational heat, so this is more for positive breeding. So instead of 6k starting heat and seeing how long it can run before meltdown, I put the slider at 9k heat. This would tie in to the timer suggestions to come up with the required starting heat for each suggested timing interval.
    The minimum timing interval would likely be heat loss over time, so would likely need to have a starting heat over the target. It may even have heat requirements that would melt parts and thus not be doable, knowing that tells you you either need to aim lower or make the timer more complex/better.
    The 80% good timer would probably be closest starting heat to the target 9k heat.
    The long timer would probably have a starting heat around 8k, since it would spend half the time under and half the time over.


    It lets the user aim for what they really care about, and tells them how to get that result. I like what's there now too, you can plug in a starting heat and see what happens. What I'm suggesting excludes that, as average operational heat dictates starting heat, and vice versa. I suggest a toggle feature, where you can change the slider from target heat to starting heat and back.

    Thanks for Giving drill access to miners!

    edited last post with old planner.


    I'm really digging this! nice work talonius.


    I can see now that my Isotope fueled positive breeder mark II design http://www.talonfiremage.pwp.b…q6e0i34xtybddwet470h6ubk0 has a tighter window than I thought, only from 5k to 5.3k for breeding isotopes in a full cycle without meltdown.


    When I was looking I noticed that the cooldown time was not working how I expected, it said no cooldown needed.

    Thanks for Giving drill access to miners!

    I've edited the timing scale slider to directly manipulate the displayed generation time, the planner will attempt to match that with an approprate cooldown time


    It will round the cooldown time to the nearest second only if doing so will result in less than 5% reduced cooling, otherwise it'll round the cooldown time UP.



    As for the starting heat, here's how the planner works under the hood.. assuming a possitive breeder:
    There's a "Heating Phase" prior to the Generation Phase where the planner assumes there are no SUC item nor SUC supply, the reactor is also concidered off. It will try to simulate the amount of lava needed to get to the desired target at a safe pace. In this phase, all components that gain heat due to the introduction of lava are flagged as "connected to hull".
    The last part of this phase will total up all the heat in the reactor and it's components.


    The Generation Phase starts as normal and will most likely stop due to critical heat levels.


    The Cooldown Phase starts and will contine until all components that were previously "connected to hull" are less than the desired starting heat, the remaining components must reach 0 heat.
    At the end of the phase the planner again totals up the heat and compares it to the value from the end of the heating phase.. the result is display on the Breeder Info tab.
    I did it this way due to the fact the components can cooldown at different speeds and if I end the cooling phase prematurely then any component that lags behind will be at risk of melting after continual use.


    You can use this heatloss stat to gauge how often you need to 'top up' the reactor with lava after each complete generating/cooling cycle. An addon to view the actual hull temperature is recomended.


    I'm unsure how to calculate the starting heat needed based on an average value, prior to running the simulation.


    Edit: Cooldown bug squished, a missing line in the data tracking class ment that data from the heating phase was bleeding over into the generation phase.

    The standalone crashes after some time trying to reset the grid.


    Intel i7 990X @ 4,60 GHZ, Asus Rampage III Black Edition, 24GB Corsair Dominator GT DDR3,
    2x Zotac Nvidia Geforce 580AMP 1,5gb, OCZ Revodrive 3 X2 240GB 1GBps,
    1TB Western Digital Cavier Black, 2x Hitachi HDS723030BLE640 3TB, 3x BenQ XL2410T LCD-Monitors


    Hosting Minecraft Servers on an Octo Core 32GB Ram Server: http://two66.com/
    Free Space available! If you need a Server let me know!

    maybe an nice feature would be the option to swich designs in the old planner to the new planner in some application (manualy doing them all is an huge task since there are so many)

    right, time to get serious...
    i wil be offline for weeks and possibly months at an time. if you have anything to add to an post i made, and would like me to know. you are welcome to pm me, and i wil reply as soon as i am able to do so.

    Quote from mijnboogje

    maybe an nice feature would be the option to swich designs in the old planner to the new planner in some application (manualy doing them all is an huge task since there are so many)



    When I believe this new planner is ready, it'll replace the old planner's location. The new planner will decode all designs made by the previous planner, if you need to look up an old design right now, you can copy the url of it and press the Paste URL button on the new planner (or alternately, Ctrl+V it into the design code text box)

    no one timer, happens all the time usually after around 10 attempts or so.

    Intel i7 990X @ 4,60 GHZ, Asus Rampage III Black Edition, 24GB Corsair Dominator GT DDR3,
    2x Zotac Nvidia Geforce 580AMP 1,5gb, OCZ Revodrive 3 X2 240GB 1GBps,
    1TB Western Digital Cavier Black, 2x Hitachi HDS723030BLE640 3TB, 3x BenQ XL2410T LCD-Monitors


    Hosting Minecraft Servers on an Octo Core 32GB Ram Server: http://two66.com/
    Free Space available! If you need a Server let me know!

    Quote from Rick

    Using google chrome

    Problem found, try firefox.

    Intel i7 990X @ 4,60 GHZ, Asus Rampage III Black Edition, 24GB Corsair Dominator GT DDR3,
    2x Zotac Nvidia Geforce 580AMP 1,5gb, OCZ Revodrive 3 X2 240GB 1GBps,
    1TB Western Digital Cavier Black, 2x Hitachi HDS723030BLE640 3TB, 3x BenQ XL2410T LCD-Monitors


    Hosting Minecraft Servers on an Octo Core 32GB Ram Server: http://two66.com/
    Free Space available! If you need a Server let me know!

    The v2 planner has been released into the wilds! ... I've randomly gone through the nuclear engineering section clicking on reacter link to check if they load up fine and so far everything seems okay.


    Now to make the page the applet sits on prettier and more informative.

    Quote from Talonius

    The v2 planner has been released into the wilds! ... I've randomly gone through the nuclear engineering section clicking on reacter link to check if they load up fine and so far everything seems okay.


    Now to make the page the applet sits on prettier and more informative.

    nice job, seems your little "project" seems to be getting an epic proporsion ;)

    right, time to get serious...
    i wil be offline for weeks and possibly months at an time. if you have anything to add to an post i made, and would like me to know. you are welcome to pm me, and i wil reply as soon as i am able to do so.

    Seems like there is a problem with the links that are on the forum now, but its fixable from the user end if they remove the "www." from the url. Check your mimetypes, or maybe domain forwarding not pushing the www sub. If you have no idea what i'm talking about(You probably do, since JAVA), get at your hosting provider and ask them to look at it.

    Hmm.. it appears the cooldown phase was interupted by a 'cell death' event.. the hull has gathered so much heat that the IHDs are suiciding themselves during the cooldown phase.


    Im going to have to think about how to catch that.


    Edit: Okay.. I think the planner now detects when there's a risk to components melting in the cooldown phase and stops the generation prematurely. In that example design the cooling cell suvives with a little over 1% 'health' left.


    Also, resources needed was fixed (the planner was doubling needed alloy) and now has the option to list 'intermediate' resources instead.