I might grab population growth (two modules, one for planets, the other for shipping)

Writing python is very like writing pseudocode. nithing to fear

I might grab population growth (two modules, one for planets, the other for shipping)

I presume we're replicating existing behaviour at the moment.
Also I recall that Hab is an integer -26<H<101 and H!=0...

I'll need a second call available to calculate the "next year pop" for the people doing the autobuild queues.

I have the working code for the RaceWizard in Javascript (and C), which includes Hab value calculations (as reverse-engineered from the EXE, refactored by me) and Terraforming (crafted by me, and apparently accurate). There's several "unit" tests, and a few comments. It should be easy to port to Python by anyone who knows Python.

I also have the Fuel Usage code, which includes travel & coords calculations (for fleets and packets), as Stars! does them. The packet part includes decay and is apparently accurate.

There's also the old Econ calculator, which includes math about max Terra, Pop, Facts, Mines, etc. Also in js.

My version of the Order of Events is a bit more "deconstructed" and has more smaller sections. We should probably compare notes ASAP.

Last but not least, the All Items Table dumper has a lot of code to deal with techs, items, engines, and hulls that could perhaps be of use somewhere.

I presume we're replicating existing behaviour at the moment.

XAPBob wrote on Mon, 02 June 2014 19:25

I might grab population growth (two modules, one for planets, the other for shipping)

Or perhaps one module, callable from two places?

Overcrowding formula?
Red planet formula?

Thanks for the pull requests! I'll add some unit tests and merge tomorrow.

Note that the planet value code is also in the javascript file (racewizard) in the docs (in the github repository), that might be easier to convert than the C code.

Yes, an array that can be appended to from eh module is about right.
Maybe a tools.message(player,message)?

XAPBob wrote on Tue, 03 June 2014 01:12

Overcrowding formula?
Red planet formula?

I have seen the math for those 2 somewhere but IIRC recently some1 posted about Resources from overcrowded planets.

Dunno if recording dmg per ship will need too much space. At any rate, the Jeffs used just 2 buckets, we could use more (in the future).

As for the messages, don't forget to add a "class" tag to them, for filtering. The more classes, the finer the graining.

I'll do it by clicks (we can then rename those pesky ambiguous low grav values at leisure).

do we want to encode the additional flexibility that the original code has (but never exposed) of having an "off centre" perfect (so you get a short tail on one side and a long tail on the other?) I think it's probably easier to add it in later if needed.

the design contains the "original armour/shield" values, so we only need two integers - It depends how constrained we feel for space of course, and with JSON it can be added later

Class per "OoE" or arbitrary class IDs (maybe prefixed by an OoE ID?)

2 questions:
Overcrowding formula?
Red planet formula?