View source for Data Aquisition from The Mirror

[[Category:Arek’Jaalan]]
{{ArekJDivisionHomePage
|divisionlogo=DivSleeperTech.jpg
|divisionname= Sleeper Technology
||ticker= ST
|projectleads= [[Cicaedis Pritchard]]
|archivists= Unknown
|levelofactivity= Active
|publicchannel= AJ: ST
|othersites= None
|researchers = [[NicolausDeWild]], [[Vanneth Deckard]], [[Kivvic]], [[Gehen_Sealbreaker_(Character)|Gehen Sealbreaker]], [[Wyke_Mossari_(Character)|Wyke Mossari]], [[Renee Khalida (Character)|Renee Khalida]], [[Rhavas_(Character)|Rhavas]]
|contributors = [[Akasha Prime]], [[Hilen Tukoss]], [[Renee Khalida (Character)|Renee Khalida]]
}}

=Project Data Acquisition From The Mirror=
 Project Lead: [[NicolausDeWild]]
 [http://www.eveonline.com/ingameboard.asp?a=topic&threadID=1563545 Project Discussion Thread]

Please feel free to share ideas, criticisms and assistance to this project by contacting NicolausDeWild via EVE Mail or by replying to the public discussion thread in the Intergalatic Summit.

==Introduction==

The gathering of all available data from Sleeper sites is of obvious importance to furthering our understanding of the Sleepers, and will likely yield insights into the other races who's remains have been encountered in wormhole space.

[[The Mirror]] is of unique interest to this effort, due to the raw volume of data that is transmitted by the structure at, so far as we are aware, all times.  The volume of data is so great that the sensor and computer systems on board all known ships to have encountered it, thus far Battleship class and smaller, are overwhelmed in their attempts to parse it in its entirety. They are forced to focus their efforts on only a small number of data streams at any given time, those with the lowest volume of data transfer, with the vast majority of the broadcast data going unrecorded let alone analyzed.

This data must be collected and analyzed.


==Project Outline==

As Battleship class vessels do not have the required sensor or computer power for this task, I propose that a Carrier class vessel be used to gather this data, as having all the hardware centralized in one ship has inherently less risk of data corruption than networking a group of Battleships.  Carriers also have the added benefit of being purpose built for receiving quantities of data beyond that of any battleship:  The drone control systems.

I recommend the use of a Chimera, for the reason it can fit the most number of Analyzer modules.  I say Analyzer modules as they are the best candidate for modification into raw signal receivers, and they possess advanced signal parsing algorithms, unlike other modules such as Codebreakers which have a much more focused feature set that makes them ill suited to this task.  Drone control units would be fitted in it's high slots, modified for our purpose into general purpose receiving arrays, with the transmitter components re-purposed into receivers also.  The standard drone control systems on board the vessel would undergo similar modification to give the ship as many metaphorical "ears" as possible.  Co-processors fill out the low slots, an Emission Scope Sharpener II rig augments the capability of the Analyzer modules and a Liquid Cooled Electronics I rig helps keep everything from melting down.

Operating all of these modules only draws approx one third of the Chimera's CPU capability, which should leave it with sufficient overhead to process the incoming data.

Making the necessary modifications to the ship and modules is outside the ability of the standard ship crews or that of a station, requiring the acquisition of  scientists to both make the modifications, and to remain on board to monitor and maintain the altered systems.

If however it is speculated that even this level of computational capacity may not be enough, the Chimera's Ship Maintenance Bay may be modified to house as many Wetware Mainframe's as the remaining powergrid can support.
 
 
The biggest hurdle to accomplishing this however is getting a properly fitted Chimera into a Class 6 wormhole that contains a Mirror structure.  Discussions on this topic have yielded two possibilities:

1) A properly fit carrier is sent through a wormhole known to lead to a Mirror structure, the problem with this is Class 6 wormholes only just barely have the required mass transit value to pass a carrier, finding one that has sufficient mass to send through a carrier and escort may prove to be an exercise in futility.

2) A wormhole leading to a Mirror structure is found, and a POS operation is set up inside the wormhole system with the purpose of constructing a carrier on site.  This may or may not be a faster method than finding a wormhole that fits the needs of 1), but has a few benefits:

	a) Having a friendly POS in the system provides a significant increase in safety to the researchers.

	b) Depending on the success of the operation to collect Mirror data, it could become a research base for long term study.

	The issues with this are that it means the POS must be defended.  It is possible we may aquire the assistance of a w-space alliance with our efforts, but such cooperation may evaporate at any time, or worse become aggression.

As of current, talks are underway to negotiate safe passage through some w-space systems that may spawn Class 6 wormholes and thus access to a Mirror structure.  Public discussion has also resulted in one pilot volunteering to build a carrier in w-space if we can acquire a location.

==Project Aims==
To tap what may be the largest source of data on the Sleepers in existence.

==Phase One:  Feasibility study -COMPLETE==

===Trial Run '''-On Hold Pending Volunteers, Primary Operation Unaffected'''===

Before committing the vast amount of resources required to acquire a Carrier and get it to a Mirror, it is necessary to do a trial run to test out the planned modification of modules and ship systems for the task.  The most able platform for a small scale test is the Widow Black Ops Battleship, thanks to its vast midslots and near Carrier levels of CPU.

Some hypothesise that this vessle itself will be enough to capture the Mirror data, if this is the case then that would save us a lot of resources.  However it's the very limited data storage ability and built-in communications arrays means it is doubtful a Widow could monitor all of the data, or store more than a few minutes, or even seconds, of it.

The fitting would be as such:

 [Widow, Mirror Breaker]
 Co-Processor II
 Co-Processor II
 Co-Processor II
 Co-Processor II

 Analyzer II
 Analyzer II
 Analyzer II
 Analyzer II
 Analyzer II
 Analyzer II
 Analyzer II
 Analyzer II

 Black Eagle Drone Link Augmentor
 Black Eagle Drone Link Augmentor
 Black Eagle Drone Link Augmentor
 Black Eagle Drone Link Augmentor
 Black Eagle Drone Link Augmentor
 Black Eagle Drone Link Augmentor
 Black Eagle Drone Link Augmentor

 Large Emission Scope Sharpener II
 Large Liquid Cooled Electronics I

UPDATE:  While still greatly desired, it is felt by those involved at this time that deploying a Widow poses too great a risk to the ship and crew for too little possibility of success.  As such, no trial run will take place unless additional volunteers come forward to provide assistance.

===Evaluate best Carrier and fitting for use in this project. '''-FINALIZED'''===

The use of a Chimera specifically is not necessary, it was chosen as the best candidate based on the hypothesis that the limiting factor in a ships ability to capture the data from a Mirror structure is it's limited number of receiver arrays, which limit the number of frequencies that can be "heard" and the data throughput.  The Chimera has the most mid slots, and so can fit the most Analyzer modules, giving it the most possible receiver arrays.  

Fitted as follows:

 [Chimera, Mirror Breaker]
 Co-Processor II
 Co-Processor II
 Co-Processor II
 Co-Processor II

 Analyzer II
 Analyzer II
 Analyzer II
 Analyzer II
 Analyzer II
 Analyzer II
 Analyzer II

 Drone Control Unit I 
 Drone Control Unit I
 Drone Control Unit I
 Drone Control Unit I
 Drone Control Unit I

 Large Emission Scope Sharpener II
 Large Liquid Cooled Electronics I
 [empty rig slot]

Such a Chimera has approximately one third of it's power grid capacity unused, and approximately two thirds of it's CPU capacity unused.  This free CPU capacity is vital as processing the signal data will be beyond the ability of the local processors in the ships standard communication arrays, the Analyzer modules or the DCUs.

If on the first attempt it is found that this amount of CPU is not sufficient, then the ships Ship Maintenance Array can be modified such that the normal data lines that would connect to a docked ship could be connected to clusters of Wetware Mainframes.

If however it is hypothesized that orders of magnitude more CPU power, or receiver arrays, are needed after the first attempt, then it may be necessary to abandon the restriction against using a group of remotely networked ships.  As using multiple Carriers would be prohibitively expensive at such a point, a large number of Battleships would be required, with the existing Carrier used as the hub of the network.

Ideas on if another class of Carrier would be better suited, or methods that would lessen the risk inherent to remotely networking multiple ships to an acceptable level, may be sent directly to NicolausDeWild via EVE Mail, or in the [http://www.eveonline.com/ingameboard.asp?a=topic&threadID=1563545&sid=554116367 Discussion Thread]

'''UPDATE:'''  Discussion has concluded that a Chimera is the best Carrier class ship for this operation, the fitting may be modified slightly to provide increased defensive capabilities, however for security reasons these changes will not be made public at this time.

===Travel to, or Build Locally? '''-FINALIZED'''===

Before we can proceed we must identify the relative feasibility of crossing a Carrier and supporting ships through a Class 6 wormhole that leads to a system with a Mirror structure, compared to organizing the construction of a carrier within such a system. 

We need:
*Pilots to recon C6 wormholes and to report back on their type, as well as any corporations that have set up shop inside or around C6 wormhole systems that contain a Mirror. -COMPLETE
*Detailed information on the resources and timeframe required to go from initial Large POS anchoring to a Carrier leaving a Capitiol Construction Yard. -COMPLETE
*Contact with industrialists willing and able to help us set up and sustain this operation. -COMPLETE
*To research potential assistance from w-space corporation(s) and/or alliance(s).  One of them may be willing to do some or all of the work while giving us access to the data. '''-IN PROGRESS, SEEKING ADDITIONAL INPUT'''

'''UPDATE:'''  Due to security and logistical concerns, the Chimera for use in this project will be constructed on site.  The carrier that has currently been modified will remain as such for further simulations and to provide a guide for the modification to a Chimera blueprint for use in producing the on site vessel.

Additional assistance for keeping the POS secure and running will always be welcome.

==Phase Two:  Finalize Plans '''-COMPLETE'''==

*Hammer out a plan of action that is most likely to succeed. -COMPLETE
*Gather necessary resources prior to initiating plan. -COMPLETE

'''UPDATE:'''  The general plan of action is finalized and agreed to by the primary project personnel at this time, the exact details are fluid due to the nature of getting to and from a w-space system, and for security reasons will not be publicly shared at this time.

==Phase Three:  Data Acquisition and Analysis -IN PROGRESS==

*Initiate plan to deploy most appropriate data capture system.
*Upon successful deployment of a data capture system, begin analyzing the acquired data and taking steps to maintain the data capture system for as long as is necessary or feasible.

==Phase Four:  Future Integration of Trinary Data Systems==

*In the event that much of the data remains gibberish, any ability to decipher trinary data must be integrated into the data collection system in the future.

==Data Assessment==
*Due to the volume of data anticipated to be recovered by this project, it is possible that there may be data relevant to a variety of departments.  All data recovered should be made available to all departments.


There is speculation regarding the nature of both the Sleepers and the apparent fall of their civilization that warrants precautions to be made to ensure our safety.  As such, all systems intended to capture, transfer, store or process (the Secure Network) the acquired data MUST be physically isolated from all other networks and transmission hardware.   All data intended for wide distribution must be screened for potential viral contamination prior to being copied from the Secure Network.

One hypothesis is that the Sleepers are an isomorphic society, without need for individual hardware unless interaction with the physical world is necessary.  The recently spotted [[Awakened Infomorph]] has led to further speculation that it may be possible for a Sleeper Infomorph to take possession of a Capsuleer clone, possibly while a Capsuleer is still resident.  As such, the Secure Network on board the data collection ship must also be isolated from command and control systems, especially the Capsuleer pilot.

==Time Frame==
===Phase One===
 Completed August 15.

===Phase Two===
 Completed Aug 22.

===Phase Three===
 Possibly indefinite depending on precise volume of useable data.

==Required Resources==
 Widow class Black Ops Battleship and pilot x1
 Carrier class ship and pilot x1 (Acquired)
 Drone Control Unit x5 (Acquired)
 Analyzer II x8 (Acquired)
 Co-Processor II (or better) x5 (Acquired)
 Large Emission Scope Sharpener II rig x1 (Acquired)
 Large Liquid Cooled Electronics I rig x1 (Acquired)
 Carrier escorts - Standard C6 class wormhole fleet, at minimum. (More Pilots Needed)
 POS with Capitol Assembly Array and defensive structures.
 Fuel for POS.
 [http://wiki.eveonline.com/en/wiki/Scientist Scientists] x50 (Acquired)
 [http://wiki.eveonline.com/en/wiki/Science_Graduates Science Graduates] x500 (Acquired)