Guide: Arcosphere Balancing: Difference between revisions

From Space Exploration
Jump to navigation Jump to search
added names of the Greek letters instead of just symbols in the folding section
 
Line 35: Line 35:


I would recommend allowing some leeway when comparing arcosphere numbers for balancing, otherwise you may find recipes being run continuously or unnecessarily. For example, if the Left to Right inversion produces more Right arcospheres, triggering the Right to Left inversion which produces more Left arcospheres triggering the Left to Right inversion etc. This can be done by using an arithmetic combinator to subtract the value for recipe inputs from the value for recipe outputs, and using a decider combinator to check if this number is greater than some small constant.
I would recommend allowing some leeway when comparing arcosphere numbers for balancing, otherwise you may find recipes being run continuously or unnecessarily. For example, if the Left to Right inversion produces more Right arcospheres, triggering the Right to Left inversion which produces more Left arcospheres triggering the Left to Right inversion etc. This can be done by using an arithmetic combinator to subtract the value for recipe inputs from the value for recipe outputs, and using a decider combinator to check if this number is greater than some small constant.
==== Basic Implementation ====
One simple basic implementation is to isolate balancing from consumption. This blueprint #REDIRECT [[Space_factories_blueprints]] must NOT have its robot network connected to Arcosphere consumption except the red Boxes at the bottom.
This blueprint keeps a minimum set of arcospheres in its network to keep balancing always possible.
The Logik is kept simple in 2 seperate objectives:
1. Balancing
2. Provision
Balancing:
There is a global red network and for every recipe a local green network.
For every recipe all the current Storage values for 2 (or 4) Input types are added and also the current storage for all 2 (or 4) outputs types are added.
Those 2 results are then subtracted to get the difference. If the difference is bigger than 3 (meaning there are more inputs than outputs) the inserter is activated to fill the gravimetric facility which will convert the input Arcs to output Arcs to lower the difference between Input types and output types.
Provisioning:
In order to keep the balancing going a minimum set or Arcs needs to be available. This is secured by provisioning. Provisioning at the bottom will only provide Arcs to the outer world if the storage has 6 or more Arcs of that type in storage.
All Arcs from the outer world will be returned by the belt at the bottom underneath the lambda provisioning.
Fresh arcs are inserted by the bottom left belt.
New robots can be inserted by the bottom middle belt.

Latest revision as of 21:34, 1 August 2025

This guide is not meant to be a blueprint for an arcosphere balancing setup, but an explanation of the principles which can allow you to design your own solution. Solutions for arcosphere balancing are considered as SPOILERS by the Space Exploration creator. For the main page, see arcospheres.








Arcospheres are a late game resource that are primarily used as a catalyst in the production of some advanced components, and in some Deep Space Science. They are not used up in these recipes, but their polarization is changed from one form to another. Additionally, the recipes may occasionally switch what polarizations they produce as outputs, effectively randomizing the arcospheres. To sustain production the arcospheres need to be balanced so you don't run out of one type.

Balancing

There are eight polarizations of arcosphere, each labeled with a greek letter:

  • λ Arcosphere lambda λ Arcosphere lambda
  • ξ Arcosphere xi ξ Arcosphere xi
  • ζ Arcosphere zeta ζ Arcosphere zeta
  • θ Arcosphere theta θ Arcosphere theta
  • ε Arcosphere epsilon ε Arcosphere epsilon
  • φ Arcosphere phi φ Arcosphere phi
  • γ Arcosphere gamma γ Arcosphere gamma
  • ω Arcosphere omega ω Arcosphere omega

Inversion

The first balancing is done through the two arcosphere inversion recipes. Four of the arcosphere polarizations are converted into the other four or vice versa:

  • zeta(ζ)+theta(θ)+gamma(γ)+omega(ω) -> lambda(λ)+xi(ξ)+epsilon(ε)+phi(φ)
  • lambda(λ)+xi(ξ)+epsilon(ε)+phi(φ) -> zeta(ζ)+theta(θ)+gamma(γ)+omega(ω)

Going forward I will call 'zeta(ζ), theta(θ), gamma(γ), omega(ω)' the Left group and 'lambda(λ), xi(ξ), epsilon(ε), phi(φ)' the Right group. Balancing these groups can be acheived by comparing the total number of 'Left' arcospheres and 'Right' arcospheres, and running the appropriate inversion recipe if there are more of one group than the other.

Folding

The second stage of balancing is eight folding recipes, which convert one arcosphere of each group into two different arcospheres, again one of each group. For example the first recipe takes one λ lambda (Right group) and one ω omega (Left group) and converts them to one ξ xi (Right group) and one θ theta (Left group).

  • λ + ω -> ξ + θ

Determining when to run a folding recipe can be acheived by comparing the number of arcospheres for each group's input and output, for this example comparing λ to ξ, and ω to θ. The recipe should be run if there are more input arcospheres than output arcospheres for both the Left group and the Right group.

I would recommend allowing some leeway when comparing arcosphere numbers for balancing, otherwise you may find recipes being run continuously or unnecessarily. For example, if the Left to Right inversion produces more Right arcospheres, triggering the Right to Left inversion which produces more Left arcospheres triggering the Left to Right inversion etc. This can be done by using an arithmetic combinator to subtract the value for recipe inputs from the value for recipe outputs, and using a decider combinator to check if this number is greater than some small constant.

Basic Implementation

One simple basic implementation is to isolate balancing from consumption. This blueprint #REDIRECT Space_factories_blueprints must NOT have its robot network connected to Arcosphere consumption except the red Boxes at the bottom. This blueprint keeps a minimum set of arcospheres in its network to keep balancing always possible. The Logik is kept simple in 2 seperate objectives: 1. Balancing 2. Provision

Balancing: There is a global red network and for every recipe a local green network. For every recipe all the current Storage values for 2 (or 4) Input types are added and also the current storage for all 2 (or 4) outputs types are added. Those 2 results are then subtracted to get the difference. If the difference is bigger than 3 (meaning there are more inputs than outputs) the inserter is activated to fill the gravimetric facility which will convert the input Arcs to output Arcs to lower the difference between Input types and output types.

Provisioning: In order to keep the balancing going a minimum set or Arcs needs to be available. This is secured by provisioning. Provisioning at the bottom will only provide Arcs to the outer world if the storage has 6 or more Arcs of that type in storage.

All Arcs from the outer world will be returned by the belt at the bottom underneath the lambda provisioning. Fresh arcs are inserted by the bottom left belt. New robots can be inserted by the bottom middle belt.