Setting up a planetary colony: Difference between revisions

Line 48:

* Place Command Center [[File:PI_YFC-PlaceCmdCtr.png|200px|frameless|right]]

* Submit [[File:PI_YFC-CmdCntrPlaced.png|200px|frameless|right]]

* Under the Build Tab, choose Extractor Control Unit (hereafter called an ECU), then click in the location you wish to place it on the map. Below the edit tab, you will see the edits pending, the change in PG and CPU that will result and the cost of these upgrades. You can make a number of changes and then submit or cancel the changes.

[[File:PI_YFC-5-MoreExtractors.png|350px|frameless|right]]

* Under the Build Tab, choose Extractors, select the type of extractor that matches the desired resource, then click in the location you wish to place it on the map. Below the edit tab, you will see the edits pending, the change in PG and CPU that will result and the cost of these upgrades. You can make a number of changes and ~~then submit or cancel the changes.~~

* Place Extractor Heads and add more ECUs if pulling multiple resources

* Place More Extractors

* ~~Right Click~~ on the node at one end of link~~, and choose "Create Link"~~. Click on the node on the other end of the link. Notice that as you stretch the link to the destination, it will tell you the length and how much CPU and Powergrid it will cost. Keep an eye on the progress of using up your CPU and ~~powergrid~~.

* Control-click on the node at one end of link. Click on the node on the other end of the link. Notice that as you stretch the link to the destination, it will tell you the length and how much CPU and Powergrid it will cost. Keep an eye on the progress of using up your CPU and Powergrid.

* You can create a route using up to 8 intermediate nodes, so you can save link costs by connecting far away nodes to the next closest node, and linking that node to the next closest, etc. until you have it connected to where you are trying to get to.

* Create Links [[File:PI_YFC-15-AllLinked.png|350px|frameless|right]]

* Choose Schematic

Line 67:

File:PI_YFC-18-SelectCmdCtrRoute.png

</gallery>

* Click on your processor, and click on the Schematic ([[File:Icon_PI_ProcessorSchematic.png]]) Icon. Use the dropdown to select your desired output product. Submit the result, at which point you will be prompted to route the ~~result~~. Click on the product to be routed, and click "Create Route", then click on the destination storage facility~~. Finally, click on "Create Route"~~.

* Click on your processor, and click on the Schematic ([[File:Icon_PI_ProcessorSchematic.png]]) Icon. Use the dropdown to select your desired output product. Submit the result, at which point you will be prompted to route the product. Click on the product to be routed, and click "Create Route", then click on the destination storage facility.

* Submit. Click on the "Submit" button in the "Edits Pending" area. You will not be able to survey until your extractors are placed permanently, ie you must commit your changes.

* Survey Extractors and Create Routes to Launchpad

Line 76:

File:PI_YFC-23-RouteProduct.png

</gallery>

* Note that you can choose extractions that produce alot in the short term, but ultimately produce less in total, or trickle in, but generate more total product in the long term, depending on how much you want to babysit the extractors, and how consistently your Processors are running. Consensus seems to lean toward ~~the~~ 24 hour extraction. We could choose the long and copious extraction easily on this planet due to its great abundance, but to demonstrate overloaded links, I am choosing the 5 hour extraction since it creates a larger point load on the links.

* Note that you can choose extractions that produce alot in the short term, but ultimately produce less in total, or trickle in, but generate more total product in the long term, depending on how much you want to babysit the extractors, and how consistently your Processors are running. Consensus seems to lean toward a 24-hour extraction period. We could choose the long and copious extraction easily on this planet due to its great abundance, but to demonstrate overloaded links, I am choosing the 5 hour extraction since it creates a larger point load on the links.

* Upgrade links (and Submit) Partway through surveying and routing, we got the message "The route can not be created as adding traffic to one of the links over which it travels would create dangerous levels of congestion." If we hover the mouse over a link it will tell us the level of usage of the link. If we click on the destination it will tell us the link usage of all the routes arriving at that destination. It would appear that we have to upgrade two links, the one just before the Storage, and the Extractor-Extractor link just upstream of that. Click on the link to be upgraded, and click on the Link-Plus icon. You will be given a quote of how much more CPU/PG this will cost. If it is acceptable, click on the Upgrade button.

File:PI_YFC-24-OverloadedLink.png

Line 96:

* Submit

* Wait 15 minutes for the Extractors to dump into storage.

* Had a little bit of ~~power~~/CPU left, so add 3 more extractors, Submit. While we are waiting, I notice we have a little bit of ~~power~~ and CPU left, so let us add some more extractors. First upgrade the link between the last extractor and the Launchpad storage, since it was at 96%, to make sure we are not going to run out of PG halfway through this operation. Notice the additional ISK cost, and the CPU and PG differencial usage lines above the submit button.

* Had a little bit of Powergrid/CPU left, so add 3 more extractors, Submit. While we are waiting, I notice we have a little bit of Powergrid and CPU left, so let us add some more extractors. First upgrade the link between the last extractor and the Launchpad storage, since it was at 96%, to make sure we are not going to run out of PG halfway through this operation. Notice the additional ISK cost, and the CPU and PG differencial usage lines above the submit button.

* Check out the Competition: While we are waiting, we could also check out who else is on the planet. The other colonies are small and subtle. Sometimes you just see an extractor here or there, sometimes you see the Command Centre. If you click on the Command Centre you can see all the nodes in their network. Right click on the background to hide or show other players colonies. Mostly you can just ignore them, except when they are sitting on top of the juicy resource node that is rightfully yours. ~~Until Dust 541, there is little to be done about this, except that if~~ you both drink from the same resource node, each gets less. This is also a danger if you place your own extractors too close to each other. For more details, see [[Planetary Interaction PvP]].

* Check out the Competition: While we are waiting, we could also check out who else is on the planet. The other colonies are small and subtle. Sometimes you just see an extractor here or there, sometimes you see the Command Centre. If you click on the Command Centre you can see all the nodes in their network. Right click on the background to hide or show other players colonies. Mostly you can just ignore them, except when they are sitting on top of the juicy resource node that is rightfully yours. If you both drink from the same resource node, each gets less. This is also a danger if you place your own extractors too close to each other. For more details, see [[Planetary Interaction PvP]].

File:PI_YFC-28-Competition.png

Line 106:

</gallery>

* Check on Processor Buffer. Ok, enough time has elapsed for the extractors to have run a cycle by now, let's check out how we are doing at building up in the Processor's buffer. [[File:PI_YFC-30-CheckOnProgress.png|350px|frameless]].

* Oh dear, I have waited too long, and it has built up enough input to get started on the processor cycle, and is building up for the next cycle already. Now we must wait 30 minutes for the ~~Output~~ to come out. In the mean time, the buffer filled up waiting for the processing cycle to complete and backlog is building in the storage. You can use this to adjust your extraction renewal schedules by letting stuff build in storage and then coming back anytime while the Processor(s) are working on that buffer of inputs to renew your Extractors. [[File:PI_YFC-31-ProcessorRunningFull.png|350px|frameless]] [[File:PI_YFC-30a-BacklogBuildingUp.png|350px|frameless]]

* Oh dear, I have waited too long, and it has built up enough input to get started on the processor cycle, and is building up for the next cycle already. Now we must wait 30 minutes for the product to come out. In the mean time, the buffer filled up waiting for the processing cycle to complete and backlog is building in the storage. You can use this to adjust your extraction renewal schedules by letting stuff build in storage and then coming back anytime while the Processor(s) are working on that buffer of inputs to renew your Extractors. [[File:PI_YFC-31-ProcessorRunningFull.png|350px|frameless]] [[File:PI_YFC-30a-BacklogBuildingUp.png|350px|frameless]]

* Horray! Product. Now you can move to [[Colony_Management#Interplanetary_Logistics|Interplanetary Logistics]] to get your stuff off planet.

[[File:PI_YFC-31-Product.png|350px|frameless]]

* Observe that this is in a really good deposit, and will be building up a backlog for the first 24 hours, and then work on that backlog over the next little while waiting for you to come back to and re-survey the extractors.

* Teardown colony. You can tear down your whole colony by deleting the Command Center. You might need to do this if you decide to upgrade your Command Center to make your operation larger. You will lose the investment you made in the old ~~command centre~~, and all the buildings you built.

* Teardown colony. You can tear down your whole colony by deleting the Command Center. You might need to do this if you decide to upgrade your Command Center to make your operation larger. You will lose the investment you made in the old Command Center, and all the buildings you built.

'''Hint:''' select the right size of Command Center first, because to deploy a new one, you must destroy the entire colony, losing all the investment you made in extractors, all unprocessed inputs stuck in the Processors,etc. It does not destroy the items that had been exported to the Customs Office, and you can deploy a new Command ~~Centre~~ immediately rather than waiting for downtime.

'''Hint:''' select the right size of Command Center first, because to deploy a new one, you must destroy the entire colony, losing all the investment you made in extractors, all unprocessed inputs stuck in the Processors,etc. It does not destroy the items that had been exported to the Customs Office, and you can deploy a new Command Center immediately rather than waiting for downtime.

Line 125:

* Expedited Transfer

Routing is an automated ~~route~~ between one node and another. Whenever there is material at the source node, it will be transfered to the destination node. When setting up automated routes, you need to watch your link usage, and upgrade the links if you run out (or transfer less stuff by doing slower extractions, or whatever). You also can not make routes between storage nodes.

Routing is an automated transfer between one node and another. Whenever there is material at the source node, it will be transfered to the destination node. When setting up automated routes, you need to watch your link usage, and upgrade the links if you run out (or transfer less stuff by doing slower extractions, or whatever). You also can not make routes between storage nodes.

Expedited Transfers can be done to any node that it makes sense to make a transfer to, in any amount. (eg you can not expedite a transfer between two extractors.) This can be used to transfer something from storage to the launch pad, from storage to a processor in the exact amount you need to fill a buffer, etc. However, you are limited in how frequently you can perform an expedited transfer. The minimum cooldown is 5 minutes, and it increases with the amount (volume) that you transfer. For every cubic meter (m3) you transfer, there is a 14.4 second cooldown, on the node doing the transfer. Experimental Data:

Expedited Transfers can be done to any node that it makes sense to make a transfer to, in any amount. (i.e., you can not expedite a transfer between two extractors.) This can be used to transfer something from storage to the launch pad, from storage to a processor in the exact amount you need to fill a buffer, etc. However, you are limited in how frequently you can perform an expedited transfer. The minimum cooldown is 5 minutes, and it increases with the amount (volume) that you transfer. For every cubic meter (m3) you transfer, there is a 14.4 second cooldown, on the node doing the transfer. Experimental Data:

* 3000x Heavy Metals (R0) 30m3: 7:12

* 264x Reactive Metals (P1) 100m3: 24:04

@@ Line 48: / Line 48: @@
 * Place Command Center  [[File:PI_YFC-PlaceCmdCtr.png|200px|frameless|right]]<br style="clear: both" />
 * Submit [[File:PI_YFC-CmdCntrPlaced.png|200px|frameless|right]]<br style="clear: both" />
-* Place Extractor Control Unit (ECU) [[File:PI_YFC-PlaceExtractor.png|350px|frameless|right]]  [[File:PI_YFC-PlaceExtractor-Placed.png|350px|frameless|right]]<br style="clear: both" />
+* Under the Build Tab, choose Extractor Control Unit (hereafter called an ECU),  then click in the location you wish to place it on the map. Below the edit tab, you will see the edits pending, the change in PG and CPU that will result and the cost of these upgrades.  You can make a number of changes and then submit or cancel the changes.
+ [[File:PI_YFC-PlaceExtractor.png|350px|frameless|right]]  [[File:PI_YFC-PlaceExtractor-Placed.png|350px|frameless|right]]<br style="clear: both" />
 [[File:PI_YFC-5-MoreExtractors.png|350px|frameless|right]]
-* Under the Build Tab, choose Extractors, select the type of extractor that matches the desired resource, then click in the location you wish to place it on the map.   Below the edit tab, you will see the edits pending, the change in PG and CPU that will result and the cost of these upgrades.  You can make a number of changes and then submit or cancel the changes.
+* Place Extractor Heads and add more ECUs if pulling multiple resources <br style="clear: both" />
-* Place More Extractors <br style="clear: both" />
 * Create Links [[File:PI_YFC-6-StartCreateLinks.png|350px|frameless|right]] [[File:PI_YFC-7-CreatingLink.png|350px|frameless|right]]  [[File:PI_YFC-8-FinalLink.png|350px|frameless|right]]
-* Right Click on the node at one end of link, and choose "Create Link".  Click on the node on the other end of the link.  Notice that as you stretch the link to the destination, it will tell you the length and how much CPU and Powergrid it will cost.  Keep an eye on the progress of using up your CPU and powergrid.
+* Control-click on the node at one end of link.  Click on the node on the other end of the link.  Notice that as you stretch the link to the destination, it will tell you the length and how much CPU and Powergrid it will cost.  Keep an eye on the progress of using up your CPU and Powergrid.
 * You can create a route using up to 8 intermediate nodes, so you can save link costs by connecting far away nodes to the next closest node, and linking that node to the next closest, etc. until you have it connected to where you are trying to get to.<br style="clear: both" />
-* Place Processor and a Launch Pad [[File:PI_YFC-9-PlaceProcessor.png|350px|frameless|right]] [[File:PI_YFC-14-PlaceLaunchpad.png|350px|frameless|right]]<br style="clear: both" />
+* Place Processor and a Launchpad [[File:PI_YFC-9-PlaceProcessor.png|350px|frameless|right]] [[File:PI_YFC-14-PlaceLaunchpad.png|350px|frameless|right]]<br style="clear: both" />
 * Create Links [[File:PI_YFC-15-AllLinked.png|350px|frameless|right]]<br style="clear: both" />
 * Choose Schematic
@@ Line 67: / Line 67: @@
 File:PI_YFC-18-SelectCmdCtrRoute.png
 </gallery>
-* Click on your processor, and click on the Schematic ([[File:Icon_PI_ProcessorSchematic.png]]) Icon.  Use the dropdown to select your desired output product. Submit the result, at which point you will be prompted to  route the result.  Click on the product to be routed, and click "Create Route", then click on the destination storage facility.  Finally, click on "Create Route".
+* Click on your processor, and click on the Schematic ([[File:Icon_PI_ProcessorSchematic.png]]) Icon.  Use the dropdown to select your desired output product. Submit the result, at which point you will be prompted to route the product. Click on the product to be routed, and click "Create Route", then click on the destination storage facility.
 * Submit.  Click on the "Submit" button in the "Edits Pending" area. You will not be able to survey until your extractors are placed permanently, ie you must commit your changes.
 * Survey Extractors and Create Routes to Launchpad
@@ Line 76: / Line 76: @@
 File:PI_YFC-23-RouteProduct.png
 </gallery>
-* Note that you can choose extractions that produce alot in the short term, but ultimately produce less in total, or trickle in, but generate more total product in the long term, depending on how much you want to babysit the extractors, and how consistently your Processors are running.   Consensus seems to lean toward the 24 hour extraction.  We could choose the long and copious extraction easily on this planet due to its great abundance, but to demonstrate overloaded links, I am choosing the 5 hour extraction since it creates a larger point load on the links.
+* Note that you can choose extractions that produce alot in the short term, but ultimately produce less in total, or trickle in, but generate more total product in the long term, depending on how much you want to babysit the extractors, and how consistently your Processors are running. Consensus seems to lean toward a 24-hour extraction period.  We could choose the long and copious extraction easily on this planet due to its great abundance, but to demonstrate overloaded links, I am choosing the 5 hour extraction since it creates a larger point load on the links.
-* Upgrade links (and Submit) Partway through surveying and routing, we got the message "The route can not be created as adding traffic to one of the links over which it travels would create dangerous levels of congestion."  If we hover the mouse  over a link it will tell us the level of usage of the link.   If we click on the destination it will tell us the link usage of all the routes arriving at that destination.  It would appear that we have to upgrade two links, the one just before the Storage, and the Extractor-Extractor link just upstream of that.  Click on the link to be upgraded, and click on the Link-Plus icon.  You will be given a quote of how much more CPU/PG this will cost.  If it is acceptable, click on the Upgrade button.
+* Upgrade links (and Submit) Partway through surveying and routing, we got the message "The route can not be created as adding traffic to one of the links over which it travels would create dangerous levels of congestion."  If we hover the mouse  over a link it will tell us the level of usage of the link. If we click on the destination it will tell us the link usage of all the routes arriving at that destination.  It would appear that we have to upgrade two links, the one just before the Storage, and the Extractor-Extractor link just upstream of that.  Click on the link to be upgraded, and click on the Link-Plus icon.  You will be given a quote of how much more CPU/PG this will cost.  If it is acceptable, click on the Upgrade button.
 <gallery>
 File:PI_YFC-24-OverloadedLink.png
@@ Line 96: / Line 96: @@
 * Submit
 * Wait 15 minutes for the Extractors to dump into storage.
-* Had a little bit of power/CPU left, so add 3 more extractors, Submit.   While we are waiting, I notice we have a little bit of power and CPU left, so let us add some more extractors.  First upgrade the link between the last extractor and the Launchpad storage, since it was at 96%, to make sure we are not going to run out of PG halfway through this operation.  Notice the additional ISK cost, and the CPU and PG differencial usage lines above the submit button.
+* Had a little bit of Powergrid/CPU left, so add 3 more extractors, Submit. While we are waiting, I notice we have a little bit of Powergrid and CPU left, so let us add some more extractors.  First upgrade the link between the last extractor and the Launchpad storage, since it was at 96%, to make sure we are not going to run out of PG halfway through this operation.  Notice the additional ISK cost, and the CPU and PG differencial usage lines above the submit button.
 <br style="clear: both" />
-* Check out the Competition: While we are waiting, we could also check out who else is on the planet.  The other colonies are small and subtle.  Sometimes you just see an extractor here or there, sometimes you see the Command Centre.  If you click on the Command Centre you can see all the nodes in their network.  Right click on the background to hide or show other players colonies.  Mostly you can just ignore them, except when they are sitting on top of the juicy resource node that is rightfully yours.  Until Dust 541, there is little to be done about this, except that if you both drink from the same resource node, each gets less.   This is also a danger if you place your own extractors too close to each other.  For more details, see [[Planetary Interaction PvP]].
+* Check out the Competition: While we are waiting, we could also check out who else is on the planet.  The other colonies are small and subtle.  Sometimes you just see an extractor here or there, sometimes you see the Command Centre.  If you click on the Command Centre you can see all the nodes in their network.  Right click on the background to hide or show other players colonies.  Mostly you can just ignore them, except when they are sitting on top of the juicy resource node that is rightfully yours.  If you both drink from the same resource node, each gets less. This is also a danger if you place your own extractors too close to each other.  For more details, see [[Planetary Interaction PvP]].
 <gallery>
 File:PI_YFC-28-Competition.png
@@ Line 106: / Line 106: @@
 </gallery>
 * Check on Processor Buffer.  Ok, enough time has elapsed for the extractors to have run a cycle by now, let's check out how we are doing at building up in the Processor's buffer.   [[File:PI_YFC-30-CheckOnProgress.png|350px|frameless]].
-* Oh dear, I have waited too long, and it has built up enough input to get started on the processor cycle, and is building up for the next cycle already.  Now we must wait 30 minutes for the Output to come out.  In the mean time, the buffer filled up waiting for the processing cycle to complete and backlog is building in the storage.   You can use this to adjust your extraction renewal schedules by letting stuff build in storage and then coming back anytime while the Processor(s) are working on that buffer of inputs to renew your Extractors. [[File:PI_YFC-31-ProcessorRunningFull.png|350px|frameless]] [[File:PI_YFC-30a-BacklogBuildingUp.png|350px|frameless]]
+* Oh dear, I have waited too long, and it has built up enough input to get started on the processor cycle, and is building up for the next cycle already.  Now we must wait 30 minutes for the product to come out.  In the mean time, the buffer filled up waiting for the processing cycle to complete and backlog is building in the storage.   You can use this to adjust your extraction renewal schedules by letting stuff build in storage and then coming back anytime while the Processor(s) are working on that buffer of inputs to renew your Extractors. [[File:PI_YFC-31-ProcessorRunningFull.png|350px|frameless]] [[File:PI_YFC-30a-BacklogBuildingUp.png|350px|frameless]]
 * Horray! Product.   Now you can move to [[Colony_Management#Interplanetary_Logistics|Interplanetary Logistics]] to get your stuff off planet.
 [[File:PI_YFC-31-Product.png|350px|frameless]]
 * Observe that this is in a really good deposit, and will be building up a backlog for the first 24 hours, and then work on that backlog over the next little while waiting for you to come back to and re-survey the extractors.
-* Teardown colony.  You can tear down your whole colony by deleting the Command Center.   You might need to do this if you decide to upgrade your Command Center to make your operation larger.  You will lose the investment you made in the old command centre, and all the buildings you built.
+* Teardown colony.  You can tear down your whole colony by deleting the Command Center. You might need to do this if you decide to upgrade your Command Center to make your operation larger.  You will lose the investment you made in the old Command Center, and all the buildings you built.
-'''Hint:''' select the right size of Command Center first, because to deploy a new one, you must destroy the entire colony, losing all the investment you made in extractors, all unprocessed inputs stuck in the Processors,etc.  It does not destroy the items that had been exported to the Customs Office, and you can deploy a new Command Centre immediately rather than waiting for downtime.
+'''Hint:''' select the right size of Command Center first, because to deploy a new one, you must destroy the entire colony, losing all the investment you made in extractors, all unprocessed inputs stuck in the Processors,etc.  It does not destroy the items that had been exported to the Customs Office, and you can deploy a new Command Center immediately rather than waiting for downtime.
@@ Line 125: / Line 125: @@
 * Expedited Transfer
-Routing is an automated route between one node and another.   Whenever there is material at the source node, it will be transfered to the destination node.   When setting up automated routes, you need to watch your link usage, and upgrade the links if you run out (or transfer less stuff by doing slower extractions, or whatever).   You also can not make routes between storage nodes.
+Routing is an automated transfer between one node and another. Whenever there is material at the source node, it will be transfered to the destination node. When setting up automated routes, you need to watch your link usage, and upgrade the links if you run out (or transfer less stuff by doing slower extractions, or whatever).  You also can not make routes between storage nodes.
-Expedited Transfers can be done to any node that it makes sense to make a transfer to, in any amount.  (eg you can not expedite a transfer between two extractors.)    This can be used to transfer something from storage to the launch pad, from storage to a processor in the exact amount you need to fill a buffer, etc.  However, you are limited in how frequently you can perform an expedited transfer.  The minimum cooldown is 5 minutes, and it increases with the amount (volume) that you transfer.   For every cubic meter (m3) you transfer, there is a 14.4 second cooldown, on the node doing the transfer.  Experimental Data:
+Expedited Transfers can be done to any node that it makes sense to make a transfer to, in any amount.  (i.e., you can not expedite a transfer between two extractors.) This can be used to transfer something from storage to the launch pad, from storage to a processor in the exact amount you need to fill a buffer, etc.  However, you are limited in how frequently you can perform an expedited transfer.  The minimum cooldown is 5 minutes, and it increases with the amount (volume) that you transfer.  For every cubic meter (m3) you transfer, there is a 14.4 second cooldown, on the node doing the transfer.  Experimental Data:
 * 3000x Heavy Metals (R0) 30m3: 7:12
 * 264x Reactive Metals (P1) 100m3: 24:04