Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Maegil]

>Fabrication_Drone_01/initiate_repair/Fabrication_drone_{02 to 10},

>Fabrication_Drone_{02 to 10}/initiate_repair/cryovault {master_control, system_interface, physical_system_connection}.

>Repair_Drone_01/initiate_optical_scan: {cryovault, reactor, fabricator}_hull_breach
>On hull_breach = Found;
>>Repair_Drone_01/initiate_repair/hull_breach;
>>Else/assist_repair/Fabrication_Drone_02.

>Repair_Drone_02/assist_repair/Repair_Drone_01.

[S34N1C]

>Fabrication_Drone_01/initiate_repair/cryovault_(master_control, system_interface, physical_system_connection).

>Repair_Drone_01/initiate_optical_scan: (cryovault, reactor, fabricator)_hull_breach
>On cryovault_hull_breach = Found;
>>Repair_Drone_01/initiate_repair/(cryovault, reactor, fabricator)_hull_breach;
>>Else/assist_repair/Fabrication_Drone_01.

>Repair_Drone_02/assist_repair/Repair_Drone_01.

>override_previous_command
>activate_program_"+1"

[The Froggy Ninja]

>Fabrication_Drone_01/initiate_repair/cryovault_(master_control, system_interface, physical_system_connection).

>Repair_Drone_01/initiate_optical_scan: (cryovault, reactor, fabricator)_hull_breach
>On cryovault_hull_breach = Found;
>>Repair_Drone_01/initiate_repair/(cryovault, reactor, fabricator)_hull_breach;
>>Else/assist_repair/Fabrication_Drone_01.

>Repair_Drone_02/assist_repair/Repair_Drone_01.

>override_previous_command
>activate_program_"+1"

>activate_program_"+1"

[TheBiggerFish]

((
>mkdir cool_stuff
>cp Watcher_AI*.*  ./cool_stuff/
))

[helmacon]

//Our drones are treaded and there is atmosphere (and assumedly gravity) loss in all sectors. Repair drones are capable of minor construction. we need to //use (R)epair drone 01 (who is assumedly next to R 02) to modify R 02 for movement in a null atmosphere condition. Assumedly, changing the treads to //some sort of propulsion system

>Repair_Drone_01/initiate_Construction: {Repair_Drone_02, Fabrication_Drone_01}/Propulsion_systems;
>On Construction_Compleate = True;
>Fabrication_Drone_01/navigate/Cryovault;
>Repair_Drone_02/navigate/reactor;

>R_01/set/int X = 2;
>R_01/for;
>R_01/if X<16;

>R_01/Run/Diagnostics/Fabrication_Drone_(X);
>R_01/X++;

>R_01/else;
>R_01/idle;
>

[The Froggy Ninja]

//Our drones are treaded and there is atmosphere (and assumedly gravity) loss in all sectors. Repair drones are capable of minor construction. we need to //use (R)epair drone 01 (who is assumedly next to R 02) to modify R 02 for movement in a null atmosphere condition. Assumedly, changing the treads to //some sort of propulsion system

>Repair_Drone_01/initiate_Construction: {Repair_Drone_02, Fabrication_Drone_01}/Propulsion_systems;
>On Construction_Compleate = True;
>Fabrication_Drone_01/navigate/Cryovault;
>Repair_Drone_02/navigate/reactor;

>R_01/set/int X = 2;
>R_01/for;
>R_01/if X<16;

>R_01/Run/Diagnostics/Fabrication_Drone_(X);
>R_01/X++;

>R_01/else;
>R_01/idle;
>

If they were designed to patch hulls they can presumably operate in vacuum.

[Carefulrogue]

/* @helmacon
A couple of reasons I don't like your suggestion: one the presumption of artificial gravity, two the modification of the repair drones. 
In detail:
Artificial gravity would imply that someone is in need of this.  We are merely an AI, and there is no indication of crew (something we should look into.)   

Modification to the drones should not be something we need to concern ourselves with.  Yes they have treads, but it's likely that they are magnetic, or they are similar to gecko boots.  Gravity wouldn't affect them, and the treads would work just fine. 

Also, "minor construction" likely means, welding, and grunt-like work.  The finer stuff needs a Fabrication drone, and the finer stuff needs the facility. 
*/

>query_specifications Repair_Drone, Fabrication_Drone;
>query ship_crew;

[helmacon]

/* We have a cryovault, so assumedly the ship has some people on board, and these people are meant to operate in the ship at some point since we usually maintain an atmosphere. Also, repairing hull damage is significantly different from repairing a hull breach. Two more things. First, reconfiguring a tread system into a rudimentary propulsion system should be fairly simple, given that it is an out of atmosphere propulsion system. You could literally just eject minute amounts of matter in the proper direction to create thrust. An automated ball launcher could act as a propulsion system in a 0 atm, 0 gravity environment. Lastly, even if the treads do work, they would limit us to the overall application of our drones. Developing a few propulsion drones early on would make them much more versatile. They would be able to operate outside the ship and away from the floors/walls. I see no downside. */

[Chiefwaffles]

Quick note: Pseudocode and stuff taken directly from real-world command prompts like the suggestions for this update are very limiting, I find. Feel free to do pseudocode and all, but I'm completely fine with regular-ish suggestions like ">repair drone 01: repair hull" or ">have mega drone 01 repair the death beam." It's slightly easy to interpret, but more importantly, it's easy to make any kind of action with it.
<-- Watcher AI - Processing Cycle 03 -->
>access_data_storage/passengers
+>query ship_crew
[Datacore] Printing passenger manifest and ship crew manifest...
ERROR: Could not find passenger manifest in expected location.
ERROR: Could not find ship crew manifest in expected location.

>[code: cool stuff]
Error: Operation not possible.

>query_specifications Repair_Drone, Fabrication_Drone
[Datacore] Retrieving data.
Repair Drone: Mag-Gecko treads. Very basic construction & repair equipment. Basic sensor suite.
Fabrication Drone: Mag-Gecko treads. Basic construction & repair equipment. Basic sensor suite.

>Fabrication_Drone_01: Repair Cryovault(master_control, system_interface, physical_system_connection)
[Robotics] ERROR: Could not locate drone software.
Located backup programming: "System Repair" and "Hull Repair".
[Robotics] Passed through order to Fabrication Drone 01 via "System Repair" command. Report expected within cycle. See Cycle Report for results.

>Repair_Drone_01: Initiate_optical_scan: (cryovault, reactor, fabricator)_hull_breach
+> On Cryovault hull breach found: Repair Cryovault hull breach.
[Robotics] Cryovault hull breach already found. Insufficient materials to commence repairing. See Cycle Report for more details.

> Repair_Drone_02: Repair fabrication drones
[Robotics] All other drones are extremely damaged - likely irreparable.

[Watcher Overseer] Creating research subprocess...
Done. Utilize Research to create Drone programs, blueprints, to perform general research, or anything else requiring dedicated processing power. Research subprocess has 10 processing units.

Cycle Report
[Robotics|Repair] Fabrication Drone 01 has finished repair evaluation of Cryovault.
Large hull breach detected. Estimated 500 cryopods impacted by hull breach. Estimated Material cost to repair: 100 Basic Metal.
Physical connection severed. Estimated Material cost to repair: 3 components.

Status
Robotics
- Repair Drone 01: Online. No orders. Drone Bay.
- Repair Drone 02: Online. No orders. Drone Bay.
- Fabrication Drone 01: Online. No orders. Cryovault.

Research
Processing Units: 10/10
- No research processes at this time.

[helmacon]

>R_01/navigate/fabrication
>R_01/collect/materials
>R_01/ storage = full;
>R_01/navigate/cryovault
>R_01/Run/Hull_Repair

>Load Research/Blueprint_Generator/Propulsion_Drone

[crazyabe]

Research: Rep/fabDrone Program: Salvage.

[Carefulrogue]

Side note on the continual mention of propulsion drones.  I think it's too earlier, and I just don't think there is a use.  The Mag-Gecko treads should be more than enough.  We can probably assume the creators of this ship predicted and planned for a situation like this, despite their prayers hoping it never happens. 

For those that don't know, never heard of, or just don't believe be look here.  The secrets to Spiderman, the common gecko, and a future military tech, if it's not already being used. 

I guess it was too much to hope for a bunch of minor leaks. 
>Restore power Fabrication: setting low;
>inventory Fabrication;
>Run Diagnostics on damaged drones, determine salvage capabilities, and flag the rest as scrap;

[RulerOfNothing]

> Repair drone 1: evaluate damage to Fabrication
> Repair drone 2: evaluate damage to Reactor
> Fabrication drone 1: survey drone wreckage for salvage
> Research subprocesses: Improved sensor suite blueprints

[The Froggy Ninja]

> Repair drone 1: evaluate damage to Fabrication
> Repair drone 2: evaluate damage to Reactor
> Fabrication drone 1: survey drone wreckage for salvage
> Research subprocesses: Improved Fabricator Drone blueprints

[Maegil]

> Repair drone 1: evaluate damage to Fabrication
> Repair drone 2: evaluate damage to Reactor
> Fabrication drone 1: survey drone wreckage for salvage
> Research subprocesses: Improved Fabricator Drone blueprints

> Query material stocks