Editing EvE-Scout Wormhole Research Center

 Note:  WIP
== Background ==
While working on the new tooling for EvE-Scout Thera/Turnur, [[User:Sky Diamond|Sky Diamond]] came across something strange. To handle Thera or any other signature scanning, information about wormhole types and their specific characteristics is required.

For this data, [http://anoik.is/ Anoik.is] and [https://whtype.info/ whtype.info] were consulted only to hear from our in-house experts that some of the data is probably incorrect.

This lead Sky to the thought that Signal Cartel has a lot of collective knowledge about wormholes along with many pilots daily traveling through J-space.  Using these corp resources, we can get our wormhole information as precise as possible with the goal to later on release that data to the public (via our currently worked on API) so other tools can use our data.

Thus, the '''EvE-Scout Wormhole Research Center (ESWRC)''' was born!

== Purpose ==
Gathering and verifying information to form our own static wormhole data collection so that we might end up one day with a cool new service to New Eden!

== Communication ==
Please see the <code>[https://discord.com/channels/152437634927427584/1113777681725665340 #research-center]</code> channel on the EvE-Scout Enclave Discord server. 

== Tentative ESWRC Roadmap ==
# Build the scanning tool for Thera and Turnur scanning
# As a side project of this, we need static wh data for the different wh-signatures (like A239, C729, K162, ...) and all their properties in a database
# This database model needs to be designed and data imported from anoik.is and/or whtype.info
# Finish 1.
# Add an editor to the wh database for a small group of people leading ESWRC
# Add a public API to our tooling so other people could use our wh data for their tools (give back, what we took from anoik.is and whtype.info)
# Add data collection to support the research; current ideas
## Evaluate if we can use the Pathfinder Discord plugin to fetch all WH sigs from people who use PF
## Figure out if we can develop a browser plugin to get the same data from TW
# Add an API for people to work on the gathered data (probably with a delay of 1 day or so, so we don't breach security)

== Where the Data Comes From (CCP) == 
* Static Data Export (SDE) from: https://developers.eveonline.com/resource
** Directory: sde/fsd/

=== Source Files ===
* File typeIDs.yaml contains object types. Key is typeID. Every wormhole type has its own id. groupIDs.yaml contains info about object groups. Key is groupID. Group ID is 988 for wormholes.
* File typeDogma.yaml contains attribute values. Key is typeID from typeIDs.yaml.
* File dogmaAttributes.yaml contains attribute names. Key is attributeID from typeDogma.yaml.

=== Workflow ===
* Find all wormhole types in typeIDs.yaml (search by groupID: 988)
* Find all attribute values for wormholes in typeDogma.yaml
* Find attribute names in dogmaAttributes.yaml

=== Example ===
 {
 "identifier": "Z971",
 "type_id": "30579",
 "wormholeTargetSystemClass": 1,
 "wormholeMaxStableTime": 960,
 "wormholeMaxStableMass": 100000000,
 "wormholeMassRegeneration": 0,
 "wormholeMaxJumpMass": 62000000,
 "wormholeTargetDistribution": 296
 }

== Possible Targets ==
Possible targets for wormholeTargetSystemClass and probably wormholeTargetDistribution are:
* C1
* C2
* C3
* C4
* C5
* C6
* C7/HS
* C8/LS
* C9/NS
* C10/Testing
* C11/Testing
* C12/Thera
* C13/Shattered systems
* C14/Sentinel
* C15/Barbican
* C16/Vidette
* C17/Conflux
* C18/Redoubt
* C25/Pochven

== Wormhole Target Distribution == 
 Note: What this value is used for is unclear, but we do have at least some interpretations.

The documentation in CCP’s data model is “This is the distribution ID of the target wormhole distribution”.

The values of this field have the following distribution (-1 is K162):
{| class="wikitable sortable"
| 1 || -1
|-
| 1 || 2925
|-
| 1 || 2926
|-
| 1 || 2927
|-
| 1 || 2928
|-
| 1 || 2929
|-
| 1 || 2930
|-
| 1 || 2931
|-
| 1 || 2932
|-
| 1 || 2933
|-
| 1 || 2934
|-
| 1 || 2935
|-
| 1 || 2936
|-
| 1  || 2937
|-
| 1 || 2938
|-
| 1 || 2939
|-
| 1 || 2940
|-
| 1 || 2941
|-
| 1 || 2942
|-
| 1 || 2943
|-
| 1 || 2944
|-
| 1 || 2945
|-
| 1 || 2946
|-
| 1  || 2947
|-
| 1 || 2948
|-
| 1  || 2949
|-
| 1 || 2950
|-
| 1 || 2951
|-
| 1 || 2952
|-
| 1 || 2953
|-
| 10 || 296
|-
| 8 || 297
|-
| 8 || 298
|-
| 1 || 2988
|-
| 1 || 2989
|-
| 8 || 299
|-
| 1 || 2990
|-
| 9 || 300
|-
| 9 || 301
|-
| 9 || 302
|-
| 10 || 303
|-
| 10 || 304
|-
| 1 || 3128
|-
| 1 || 628
|-
| 1 || 629
|-
| 4 || 709
|-
| 5 || 731
|}

=== What We Know ===
* -1: K162 (1)
* 296: C1  & C13 J-Space (count 10, 8 types covering 4(3+1) regions, 37(34+3) constellations, 383(358+25) systems) 
* 297: C2 J-Space (count 8, 8 types covering 5 regions, 56 constellations, 537 systems)
* 298: C3 J-Space (count 8, 8 types covering 7 regions, 78 constellations, 506 systems)
* 299: C4 J-Space (count 8, 9 types covering 8 regions, 80 constellations, 523 systems)
* 300: C5 J-Space (count 9, 9 types covering 6 regions, 66 constellations, 532 systems)
* 301: C6 J-Space (count9, 9 types covering 1 region, 15 constellations, 118 systems)
* 302: C7 HS Space (count 9, 9 types covering 1193 systems)
* 303: C8 LS Space (count 10, 11 types covering 687 systems)
* 304: C9 NS Space (count 10, 11 types covering 3321 systems)
* 628: C10  QA A - For testing, count 1
* 629: C11. QA B - For testing, count 1
* 709: C12. Thera (count 4, 5 types covering 1 system)
* 731: C14-18 Drifter (count 5, 5 types covering 5 systems)

C729
* 3128: Leads only to Turnur
* 2925-2948 & 2988-2990: C25 leads to Trig Space from known-space, type C729 (reverse)
* 2951-2952: C25 leads to Trig Space from C2-6, type F216 (reverse)
* 2952: C25 C25 leads to Trig Space from Drifter Hives, type U372 (reverse)
* 2949: C25 Leads to NS from Trig Space, type X450
* 2950: C25 Leads to C4 from Trig Space, type R081
* J244 has wTD of both 303 and 3128, I assume as it can occasionally spawn leading to Turnur.

So most class systems only have one wTD, except for Turnur (special case) and of course Trig space. Let’s rephrase that: Turnur has its own wTD in the same way as Thera, but obviously Thera has its own class (C12)

== Wormhole Target System Class == 
The values of this field have the following distribution (-1 is K162):
{| class="wikitable sortable"
| 1 || -1 
|-
| 8 || 1 
|-
| 1 || 10
|-
| 1 || 11
|-
| 5 || 12
|-
| 1 || 13
|-
| 1 || 14
|-
| 1 || 15
|-
| 1 || 16
|-
| 1 || 17
|-
| 1 || 18
|-
| 8 || 2
|-
| 30 || 25
|-
| 8 || 3
|-
| 9 || 4
|-
| 9 || 5
|-
| 9 || 6
|-
| 9 || 7
|-
| 11 || 8
|-
| 11 || 9
|}

== Further Thoughts and Explanations ==
* C729 has 27, F 216 has 2, and U372 has 1 wTD. making 30 wTD's to enter Pochven.

* U372 doesn't seem an issue as it's just the one wTD.

* F216 has 2, I have near zero knowledge of Trig holes in Drone regions. Why are there 2 wTD's? This needs looking into, or someone else may know that they only lead into say interior and border systems or something?

* C729 has 27 wTD's, but 3 of these have higher numbers, almost as an afterthought. With 3 home systems, could these wTD's refer to these?

That leaves 24 wTD's and 22 systems, could that be one wTD for each system with 2 left over? Maybe either 2 "test" wTD's or even 2 Trig systems we don't know about?

Pilots may notice though that an F216 always leads to a subset of Pochven, hence the 2 wTD's but that would be gained from experience.

== Research Topics So Far ==
'''Nerialka''' - 
I recently traveled to J145706 and it had only one WH signature (my entrance) , a H296 (its listed static in anoik.is)

'''Amelia Nightingale''' -
J005926 is listed in tripwire and other places as a Pulsar, but a screenshot was shared [on the praisebob discord server] showing it as a Red Giant. I haven't stumbled across this system yet to verify.

'''Das d'Alembert''' -
J011355 is connected to Thera and I've just confirmed the statics: they are x877/c247/k346 (not k329 as I had it above). I wonder if the fact it has a k346 (which usually appears in c3) is related to it having c3 sites? J010556 is also connected to Thera, has c3 sites and c3 static WH types (in addition to c4 ofc). Both are in the same constellation. Would be interesting to see if all in that constellation have c3 sites/statics, and if a different c4 shattered constellation has all c5 sites/statics…addendum: actually, almost certainly they can’t have c5 statics, as that would mean XL WHs into c4 space!

'''Das d'Alembert''' -
Anomalous C1 wormhole spawns: over the last year-and-a-half or so I’ve noticed c1 wormhole types (O883, L614, S804 seen so far) spawning in Null Sec (mostly) and Low Sec (once). It appears that at least under certain circumstances these types can spawn outside of c1 space. Once two such wormholes were observed in the same system and once there was another in a different system in the same constellation. So far the systems were they have been seen to have spawned are:

* DP-1YE
* Jamunda
* NCG-PW
* NJ4X-S
* P3EN-E
* PNS7-J
* RLTG-3
* S-EVIQ

One of the most recent observations (NCG-PW) had a weak [https://wiki.eveuniversity.org/Metaliminal_Storms Metaliminal plasma storm] in the system, but AFAICR none of the others did. RLTG-3 (same constellation), which also had an anomalous spawn, did not.

See these read-only forum threads for more info:
</br>https://forums.eveonline.com/t/wormholes-by-type-tool/327596 (mostly later posts)
</br>https://forums.eve-scout.com/topic/10064/strange-wormhole-spawns