Does anyone know about the size/volume of the bubble/pill of inhibated systems

[CMDR Byr Goefin]

Is there any way to work it out from powerplay, CC's?

That is how I did my estimate, but there are lots more systems out of PP sphere

 

[Winterwalker]

That is how I did my estimate, but there are lots more systems out of PP sphere

True .. but you've got "most" of the heavily populated systems covered i think?
Maybe add a small percent? As a total guess, add +5%?

edit -- probably much less than that, generally they're extraction/refinery systems outside?
1% is probably over the max .. and less than that, your original estimate(s) fall inside margin of error? (required accuracy depends on what you want the number for)

 

[tricky]

A *round* 60 million cubic light years, should do just fine I'd say.

That skews the average a tiny bit toward the second, more sophisticated figure ..
.. but is one smexy number!

I was going to go with the average of 3 spheres too.

Could have used the proper formula for an ellipsoid, (4/3 . pi) . a . b . c, but that gives a smaller number.

Just did a quick calculation for the mass of the bubble. Just for fun.

The average mass of our galaxy per cubic light year, M[SUB]A[/SUB] = 8x10²⁹ kg/LY³
Volume of bubble, V = 60,000,000 cubic LY

therefore,

Mass of the bubble, M = M[SUB]A[/SUB] . V

= 8x10²⁹ . 6x10⁷
= 4.8x10³⁷ kg

I'll let the reader work out the zeros.

 

[wolverine2710]

Posted this also in the TD thread here, but haven't got a reply yet. As we are on a roll here I thought why not ask it here also ;-)

I'm not sure what kind of algorithms all the trading tools use but I know that Trade Dangerous (TD) uses the knapsack algorithm which is NP-complete/NP-hard. NP-complete means that in worst for every station added the computation time can grow exponentiallly (did some RTFM). Hence AFAIK to get acceptable calculation times ONLY for a radius around your current position (sphere) knapsack is used and the best trading routes calculated.
Does anyone know the default radius for the sphere size for this calculation for TD?
Iirc for BPC one could set a LY radius for the sphere. Anyone knows the default radius?
Some goes for the other trading tools. If someone knows some details for the other trading tools that would be great.

This together with some stats from Madado's Market Share (MMS) I can hopefully calculate some info to put everything in perspective for the mentioned "open letter" thread. Atm we do NOT have data for all the stations (PRE Horizons), not even now that 99.999 percent of all data is coming from the iphone companion app api tools. I believe with Horizons there will be LOTS more market and iirc with horizons the number of commodities has increased. Putting an even higher pressure on knapsack etc...

 

[wolverine2710]

A *round* 60 million cubic light years, should do just fine I'd say.

That skews the average a tiny bit toward the second, more sophisticated figure ..
.. but is one smexy number!

60 million cubic light it is then.....

 

[CMDR Byr Goefin]

60 million cubic light it is then.....

What's a cubit?

[video=youtube_share;so9o3_daDZw]https://youtu.be/so9o3_daDZw[/video]

 

[Winterwalker]

What's a cubit?

I've a funny feeling old Mr Huxtable there will soon be occupying a volume somewhat smaller that 60 million cu Ly's .. more like 8 foot by 10 for the forseeable?

I'm not sure what kind of algorithms all the trading tools use but I know that Trade Dangerous (TD) uses the knapsack algorithm which is NP-complete/NP-hard. NP-complete means that in worst for every station added the computation time can grow exponentiallly (did some RTFM). Hence AFAIK to get acceptable calculation times ONLY for a radius around your current position (sphere) knapsack is used and the best trading routes calculated.
Does anyone know the default radius for the sphere size for this calculation for TD?
Iirc for BPC one could set a LY radius for the sphere. Anyone knows the default radius?

Afraid I can't help you there (in fact I can barely understand it! ).
Probably a direct message to the App Creator (through your ED Codex Pages) gets you that answer?
Hopefully this gives it a bump though. Good luck.

 

[DNA-Decay]

Perfecto. This estimate is very useful for me. Will be used in a upcoming post in the "Open Letter to Frontier Developments" thread to put things a bit in perspective.

I'd hold off until FDev are all back from holidays.
That's a great thread, but I think it will take FDev a while to wade through it.
Needs proper thought and a brainstorming session by FDev, you want the senior smart folks on deck for that.
I assume they're waking up naked on a beach in Ibizia about now.
or Phuket, or Hoi An or Kuta or Goa or I dunno maybe they went skiing.

 

[wolverine2710]

I'd hold off until FDev are all back from holidays.
That's a great thread, but I think it will take FDev a while to wade through it.
Needs proper thought and a brainstorming session by FDev, you want the senior smart folks on deck for that.
I assume they're waking up naked on a beach in Ibizia about now.
or Phuket, or Hoi An or Kuta or Goa or I dunno maybe they went skiing.

As said in the "open letter" thread they asked us for input on requirements for an official api on the 15th of Januari 2015. On the 19 th of Februari 2015 Michael Brookes closed the thread with the following words: "Thread closed so I can begin the internal process reviewing the input on this thread. Thanks to everyone who has participated. We obviously have a lot of work going on so I anticipate it being a few weeks before the next update on this. I'll post when we have something. Thanks! Michael". FD employees also told us recently that the API has been discussed in the last weeks or so. Hence they MUST have a good understanding of what information they want like to give us - at some point. They also know full well the incredible and quite mature (data sharing) eco-system out there. Hence they know what the consequences of giving us certain data will be - and if it fits their design of the game. A full blown API will take them time but I sincerely hope that they start take the third party tool authors seriously (and start to help us) and at least give us a "dump api" as a stop gap solution. If not commanders will continue to use the iPhone companion api unless they sent cease and desist letters to all tool authors who created the api tools and tool authors which use the data indirectly - EDDN, EDDB EDSM etc. They could also start banning commanders. For sure a clear signal to the ED community and the internet at large. More detailed info here. I'm not sure if they will or want to go that road but it is their game and they have every right to do so.... Imho and personal oponion they so far have tolerated the usage of the api tools without telling us that they do.....

But that is of course a discussion best suited for the "open letter" thread - not here!!!
Thanks for all the help commanders.