1094 over-exuberant resource movement

[erstad]

When the attached save is run with 1094, the amount of resources in osaka/kobe and tokyo goes to over 900K each.

Unless the 999K cap has been removed, this is going to limit the ability to drop off resources in those hexes. Which means one will have to drop off resources in other hexes. Which means a net increase in overland movement requirements. Which means a net increase in lossage during transport.

Couldn't there be a cap on the resource draw of some number of days of usage, so that the hex doesn't "fill up" and we can continue to run convoys to where the resources get used?

Of course, removing the 999K cap would also be an option. But only if the hexes didn't then steal to the next higher limit and/or absorb everything in sight.

[jwilkerson]

ORIGINAL: erstad

When the attached save is run with 1094, the amount of resources in osaka/kobe and tokyo goes to over 900K each.

Unless the 999K cap has been removed, this is going to limit the ability to drop off resources in those hexes. Which means one will have to drop off resources in other hexes. Which means a net increase in overland movement requirements. Which means a net increase in lossage during transport.

Couldn't there be a cap on the resource draw of some number of days of usage, so that the hex doesn't "fill up" and we can continue to run convoys to where the resources get used?

Of course, removing the 999K cap would also be an option. But only if the hexes didn't then steal to the next higher limit and/or absorb everything in sight.

Actually, the easier solution may be to remove the transport loss for resources - that is what we're considering at this point.

[erstad]

That'd help but without removing the 999,999 cap it'll still be difficult to use those two very nice ports as termini.

[seydlitz_slith]

why not three more nines to the cap?

[pompack]

ORIGINAL: jwilkerson

ORIGINAL: erstad

When the attached save is run with 1094, the amount of resources in osaka/kobe and tokyo goes to over 900K each.

Unless the 999K cap has been removed, this is going to limit the ability to drop off resources in those hexes. Which means one will have to drop off resources in other hexes. Which means a net increase in overland movement requirements. Which means a net increase in lossage during transport.

Couldn't there be a cap on the resource draw of some number of days of usage, so that the hex doesn't "fill up" and we can continue to run convoys to where the resources get used?

Of course, removing the 999K cap would also be an option. But only if the hexes didn't then steal to the next higher limit and/or absorb everything in sight.

Actually, the easier solution may be to remove the transport loss for resources - that is what we're considering at this point.

Joe:
Just ran some more tests: 1094b, H2H, Scen 1, all a/c grounded and no orders issued

Usual format problem

date (resource-pool) (loss) (cum-loss) (avg-loss) (6-day-avg-loss)
7-Dec-41 7322400
8-Dec-41 7283719 38681 38681 38681
9-Dec-41 7200154 83565 122246 61123
10-Dec-41 7160616 39538 161784 53928
11-Dec-41 7118737 41879 203663 50916
12-Dec-41 7106854 11883 215546 43109
13-Dec-41 7089474 17380 232926 38821 38821
14-Dec-41 7075643 13831 246757 35251 34679
15-Dec-41 7064124 11519 258276 32285 22672
16-Dec-41 7044046 20078 278354 30928 19428
17-Dec-41 7031257 12789 291143 29114 14580
18-Dec-41 7011352 19905 311048 28277 15917
19-Dec-41 6999569 11783 322831 26903 14984

The pools for the ports of Port Author, Kobe, Osaka, Tokyo, Hokadata, Fukoaka all in the 900k region by 11 dec.

Now what the numbers seem to say is that enormous numbers of resources move to these ports until they fill up or the source bases dry up. After that the movement and associated wastage is due to daily resource use at the destinations and daily resource production at the sources.

My estimate is that removing the transport loss for movement would address the wastage problem. Increasing the cap at the destination ports would allow all of the available supply to move to these designated ports leaving no pools anywhere else. While this could have unforeseen consequences for factory supply, it is nothing that will not happen anyway if the overall stockpile is reduced to the point where all resources would fit in the designated ports under the existing cap.

[Nomad]

fixed formatting

Code: Select all

 date        (resource-pool)   (loss)   (cum-loss)    (avg-loss)   (6-day-avg-loss)
 7-Dec-41        7322400
 8-Dec-41        7283719        38681     38681         38681
 9-Dec-41        7200154        83565    122246         61123
 10-Dec-41       7160616        39538    161784         53928
 11-Dec-41       7118737        41879    203663         50916
 12-Dec-41       7106854        11883    215546         43109
 13-Dec-41       7089474        17380    232926         38821        38821
 14-Dec-41       7075643        13831    246757         35251        34679
 15-Dec-41       7064124        11519    258276         32285        22672
 16-Dec-41       7044046        20078    278354         30928        19428
 17-Dec-41       7031257        12789    291143         29114        14580
 18-Dec-41       7011352        19905    311048         28277        15917
 19-Dec-41       6999569        11783    322831         26903        14984 
 

[pompack]

ORIGINAL: Nomad

fixed formatting

How'd you do that?

[Nomad]

put code and /code , both in brackets [] around the formatted text - do a quote on my post to see.

[pompack]

neat

But will I remember tomorrow? [&:]