HIP 8525; (backtrack BD+77 84)(backtrack Cephei Sector DQ-Y b2)(backtrack Bumbo)(backtrack HIP 2422)(backtrack Cephei Sector DQ-Y b6)(backtrack Gliese 3050)
Yes
Rather than going for Poqomathi, HIP 8525 goes for HIP 2422 (4th rather than 5th on the list, both inhabited)
Like Ixbalan, there seems to be some tendency for Controls with a lot of target options to not necessarily attack the furthest possible.
Looking way back to the 13th July when HIP 8525 last attacked, HIP 2422 was still in cooldown from an earlier defeated Alert, and BD+77 was in Recovery, so we don't have an exact precedent.
A rule that NAF attacks can't attack further than the fourth target would explain all weeks at HIP 8525 (and HIP 7338) and still allow Tougeir's attacks on Jeng without breaking anything else ... but isn't sufficient to explain Ixbalan which was consistently attacking target 2 of 3. HIP 2422 is inside the sphere already set by HIP 11111 ... but again, that doesn't explain Ixbalan where it was placing the furthest Alert for Taranis either way every time.
With Indra and Cocijo likely to be entering NAF mode more often, and having fairly densely connected areas, we might get a bit more data to work with soon.
Systems are listed in order of priority, and in general the first five would be expected to be hit by Alerts. Predictions made early in the week may be reissued later if Control recaptures materially affect them. If the Control Sphere Edge is reached and targeting mode switches, predictive confidence is lower and the consequences of recaptures may be more significant.
Table key
Name: Name of system considered at threat of Alert. Bold if in Control-based prioritisation it would be eligible for backtrack targeting. Distance: The distance in LY to the Maelstrom. A primary component of Thargoid prioritisation. Attackers: A list of potential Controls to launch the attack from, partial if there are 4 or more. Controls disconnected from their parent maelstrom are marked in italics; controls attacking a system closer to the maelstrom than themselves are underlined; controls which may be skipping an inner uninhabited system to strike an inhabited system further out are struck-through; controls containing a barnacle matrix are bold. Once targeting switches to Control-based rather than Target-based prioritisation, only one is listed here. Inhabited: Whether the system contains standing human population.
No model changes, though HIP 8525 adds to Ixbalan the evidence that "attacks furthest" isn't quite the right priority rule here. Without more data that'll just be something to highlight in cases where a Control in "outside" mode has lots of targets.
-------------------------------------------
Calculating Taranis
Read 14 control systems and 979 targets.
Total connected: 6 Disconnected Controls
Nominally four Alerts at Taranis this week (since the backtracks from BA-A d85 aren't usable) - that won't last through the planned attacks, but it will almost certainly get to play its two strongest. Most of the disconnected controls are in the Hupang cluster.
-------------------------------------------
Calculating Leigong
Read 16 control systems and 976 targets.
Total connected: 9 Disconnected Controls
Indra should stay in internal mode this week, as it's on the inner part of its cooldown cycle and even the reserves here are a long way from the nominal edge. No inhabited targets, which is rare for it.
-------------------------------------------
Calculating Oya
Read 25 control systems and 968 targets.
Total connected: 24 Disconnected Controls
A usable backtrack suggests five Alerts here, with potential to swap BV-Y b2 for Aowicha if the isolated Akbakara gets removed like Liu Huang was.
-------------------------------------------
Calculating Cocijo
Read 57 control systems and 938 targets.
Total connected: 56 Disconnected Controls
System
Distance
Col 285 Sector WY-F b12-1
20.85255624
Furthest Control: 21.999 LY
Target
Target Distance
Control Distance
Attackers
Inhabited?
Col 285 Sector WY-F b12-5
19.034
17.824
Mapon;
No
-
-
-
Control Sphere Edge
-
Col 285 Sector XT-Q c5-6
25.235
16.365
Col 285 Sector VN-H b11-4; (backtrack Col 285 Sector VN-H b11-0)
No
Col 285 Sector XT-Q c5-2
24.746
16.621
Ulche; (backtrack Col 285 Sector XT-Q c5-1)(backtrack Col 285 Sector UN-H b11-6)
No
Col 285 Sector VN-H b11-0
25.038
17.735
Col 285 Sector VN-H b11-7;
No
Col 285 Sector KM-V d2-69
23.672
17.774
Col 285 Sector SS-H b11-6; (backtrack Col 285 Sector QX-H b11-2)
Yes
Paitra
24.880
18.193
Col 285 Sector UN-H b11-4; (backtrack Col 285 Sector XT-Q c5-22)(backtrack HIP 36901)(backtrack Col 285 Sector WT-Q c5-22)
Yes
Col 285 Sector RS-H b11-6
26.660
18.572
Col 285 Sector VY-Q c5-18; (backtrack Col 285 Sector SS-H b11-0)(backtrack Col 285 Sector SS-H b11-3)(backtrack Col 285 Sector SS-H b11-2)(backtrack Col 285 Sector VY-Q c5-19)
No
Col 285 Sector AU-F b12-6
28.194
20.745
HIP 38235; (backtrack Col 285 Sector AU-F b12-2)(backtrack Col 285 Sector AU-F b12-5)(backtrack Col 285 Sector AU-F b12-3)(backtrack Col 285 Sector AU-F b12-4)(backtrack Col 285 Sector AU-F b12-7)(backtrack Col 285 Sector CA-P c6-16)
No
Col 285 Sector PM-J b10-3
29.712
20.772
Col 285 Sector TS-H b11-6; (backtrack Col 285 Sector VY-Q c5-2)
No
Col 285 Sector UD-G b12-2
25.947
20.853
Col 285 Sector WY-F b12-1; (backtrack 19 Puppis)
Yes
Cocijo hits the edge early, but has usable backtracks.
-------------------------------------------
Calculating Thor
Read 36 control systems and 957 targets.
Total connected: 32 Disconnected Controls
If I may ask, has there been any further insight regarding attacks which occur beyond 10 light-years?
The reason for asking began with V mentioning yesterday that INTRA was doing something wrong at M. Indra; I thought to help discover what occurred, and found that it differs from the week 47 revision, where it has HIP 20890 still being attacked by HR 1354 rather than being guarded. Of course, its original week 47 was different with the cleared HIP 20679 not being an attacker of HIP 20890.
Looking backward, despite the targets matching there were attacker differences on the previous week—and the week before that—arriving eventually at week 41 where HR 1354 attacks HIP 20741 at 10.023 Ly, the lack of which propagates to report a wrong target six weeks later. I thought you may enjoy knowing a specific example where a strict version of events causes things to go awry, and the known-to-be-spurious behaviour actually makes a tangible difference!
Interesting - so HR 1354 definitely was the over-range attacker in week 41, then? I must have quietly assumed it was without picking up on the significance at the time... That would at least give a second case of "does occur", which might help narrow things down.
Most of the other examples - often at lower ranges - have turned out not to attack, at least where such has been provable.
I stopped just a bit short of saying yes, and took a further look—the mismatches go all the way back to week 33, which had two long-range attackers and has deviated ever since! Week 32 is the latest which seems to match, although since week 33 there are around a half-dozen cases to consider, and I imagine it would be a bit presumptuous to suppose that any particular case definitely occurred.
I will leave that with V to try different combinations and find which are needed to explain the Alerts, although that may be unlikely at this point and it may remain a simple trivium that at least one of those long-range cases occurred somewhere.
For about the first time since we started having usable predictions, no material changes were expected as a result of this week's recaptures. All predictions [edit, except Cocijo] accurate this week.
I feel so terribly bad for this—one may need to review M. Cocijo and Col 285 Sector XT-Q c5-6.
Additional: Given that Col 285 Sector XT-Q c5-2 can only have been attacked by Ulche, it appears as if Col 285 Sector UN-H b11-4 has attacked Col 285 Sector XT-Q c5-1 instead.
Yes, good point - with them both being XT-Qs I must have skimmed over that.
Hmm. VN-H b11-4 doesn't attack, that makes VN-H b11-0 not a backtrack, so the backtrack Ulche places when attacking XT-Q c5-2 instead has to be used to get a 5th attack.
So the question is, why didn't VN-H b11-4 attack? The most likely explanation, given how many systems which were attacked last week it's next to, is that it was resting from attacking one of those, and one of last week's attacks was misattributed to one of the other nearby controls, possibly because of some complicated cascade like at Indra.
If you have a straightforward way to check for that sort of error, great - if not, we'll just have to see what happens next.
Systems are listed in order of priority, and in general the first five would be expected to be hit by Alerts. Predictions made early in the week may be reissued later if Control recaptures materially affect them. If the Control Sphere Edge is reached and targeting mode switches, predictive confidence is lower and the consequences of recaptures may be more significant.
Table key
Name: Name of system considered at threat of Alert. Bold if in Control-based prioritisation it would be eligible for backtrack targeting. Distance: The distance in LY to the Maelstrom. A primary component of Thargoid prioritisation. Attackers: A list of potential Controls to launch the attack from, partial if there are 4 or more. Controls disconnected from their parent maelstrom are marked in italics; controls attacking a system closer to the maelstrom than themselves are underlined; controls which may be skipping an inner uninhabited system to strike an inhabited system further out are struck-through; controls containing a barnacle matrix are bold. Once targeting switches to Control-based rather than Target-based prioritisation, only one is listed here. Inhabited: Whether the system contains standing human population.
-------------------------------------------
Calculating Taranis
Read 13 control systems and 979 targets.
Total connected: 6 Disconnected Controls
Very favourably, Taranis is placing two of its three Alerts from its peripheral controls, so if the recapture goes entirely according to plan this week, only one Alert will be placed - which means it is not critical to prevent an invasion at Njorog, provided that at least two of the four current Alerts are held off.
-------------------------------------------
Calculating Leigong
Read 16 control systems and 978 targets.
Total connected: 9 Disconnected Controls
Col 285 Sector SS-H b11-7; Col 285 Sector VY-Q c5-18;
No
Kurumanit
20.237
20.853
Col 285 Sector WY-F b12-1;
Yes
Col 285 Sector SS-H b11-5
20.306
12.899
Col 285 Sector SS-H b11-1; Col 285 Sector VY-Q c5-15; Col 285 Sector VY-Q c5-17; etc
No
Col 285 Sector SS-H b11-4
20.309
14.428
Col 285 Sector VY-Q c5-15; Col 285 Sector VY-Q c5-17; Col 285 Sector VY-Q c5-18;
No
Col 285 Sector ZT-F b12-4
21.191
16.728
Col 285 Sector ZT-F b12-3; HIP 38235;
No
Col 285 Sector UN-H b11-2
21.222
18.572
Col 285 Sector VY-Q c5-18;
No
Col 285 Sector BF-E b13-0
21.416
11.908
Col 285 Sector OS-T d3-117; Col 285 Sector OS-T d3-144; Col 285 Sector OS-T d3-137;
No
Col 285 Sector BA-P c6-16
21.655
16.153
Col 285 Sector OS-T d3-143;
No
We may have some errors with which Controls are able to act at Cocijo, though this week has relatively few candidates on what should be an internal-only week, so might give some chance for that to straighten out.
-------------------------------------------
Calculating Thor
Read 36 control systems and 958 targets.
Total connected: 32 Disconnected Controls
HIP 19894 doesn't attack SM-C b13-0
The other four of the top five attacks appear to proceed normally, then the HIP 21125 backtrack is used by JA-G b11-1
This isn't explainable by the current theory even under data entry error conditions: the Rajuarpai sub-cluster only has two external targets (plus a third once HIP 20024 recovers)
- SM-C b13-0 can be attacked by Chanyaya, HIP 19894, and IG-O c6-14
- JG-O c6-5 (alerted last week) can be attacked by Chanyaya and IG-O c6-14 only (and presumed to be attacked by Chanyaya)
So HIP 19894 is closer in to Thor than most other controls (IG-O c6-14 is too far out if HIP 19894 passes, though), can't still be cooling down from an attack in the previous week, and apparently made this attack successfully 3 weeks ago (again, in a week where swapping that attack to IG-O c6-14 would have put it too far down the list)
Another reminder that our theory for outside attacks isn't quite complete.
Systems are listed in order of priority, and in general the first five would be expected to be hit by Alerts. Predictions made early in the week may be reissued later if Control recaptures materially affect them. If the Control Sphere Edge is reached and targeting mode switches, predictive confidence is lower and the consequences of recaptures may be more significant.
Table key
Name: Name of system considered at threat of Alert. Bold if in Control-based prioritisation it would be eligible for backtrack targeting. Distance: The distance in LY to the Maelstrom. A primary component of Thargoid prioritisation. Attackers: A list of potential Controls to launch the attack from, partial if there are 4 or more. Controls disconnected from their parent maelstrom are marked in italics; controls attacking a system closer to the maelstrom than themselves are underlined; controls which may be skipping an inner uninhabited system to strike an inhabited system further out are struck-through; controls containing a barnacle matrix are bold. Once targeting switches to Control-based rather than Target-based prioritisation, only one is listed here. Inhabited: Whether the system contains standing human population.
-------------------------------------------
Calculating Taranis
Read 7 control systems and 989 targets.
Total connected: 3 Disconnected Controls
A substantial disconnected region has formed at Indra with last week's Spire recaptures, and the edge starts to get close to being relevant - though not quite yet.
-------------------------------------------
Calculating Oya
Read 25 control systems and 970 targets.
Total connected: 24 Disconnected Controls
HIP 8525; (backtrack BD+77 84)(backtrack Cephei Sector DQ-Y b2)(backtrack Bumbo)(backtrack HIP 2422)(backtrack Cephei Sector DQ-Y b6)(backtrack Gliese 3050)
Yes
HIP 21386
20.509
18.170
Akbakara;
No
None of the first four place backtracks, so Oya shouldn't place a fifth this time.
-------------------------------------------
Calculating Cocijo
Read 57 control systems and 937 targets.
Total connected: 56 Disconnected Controls
System
Distance
Col 285 Sector WY-F b12-1
20.85255624
Furthest Control: 21.999 LY
Target
Target Distance
Control Distance
Attackers
Inhabited?
Col 285 Sector UN-H b11-5
19.376
16.621
Ulche; Col 285 Sector UN-H b11-4;
No
Col 285 Sector YT-F b12-6
20.034
17.824
Mapon;
No
Col 285 Sector SS-H b11-4
20.309
14.428
Col 285 Sector VY-Q c5-15; Col 285 Sector VY-Q c5-17; Col 285 Sector SS-H b11-6; etc
No
Mahlina
21.146
15.964
Col 285 Sector VY-Q c5-17;
Yes
Col 285 Sector ZT-F b12-4
21.191
16.728
Col 285 Sector ZT-F b12-3; HIP 38235;
No
Col 285 Sector UN-H b11-2
21.222
18.193
Col 285 Sector UN-H b11-4; Col 285 Sector VY-Q c5-18;
No
Col 285 Sector BF-E b13-0
21.416
11.908
Col 285 Sector OS-T d3-117; Col 285 Sector OS-T d3-144; Col 285 Sector OS-T d3-137;
No
Col 285 Sector BA-P c6-16
21.655
16.153
Col 285 Sector OS-T d3-143;
No
Col 285 Sector ZT-F b12-2
21.760
20.745
HIP 38235;
No
-
-
-
Control Sphere Edge
-
Col 285 Sector XT-Q c5-6
25.235
16.365
Col 285 Sector VN-H b11-4;
No
All looking fairly normal at Cocijo. Hopefully the last week has shaken out any residual data issues - although, with the oddity at Thor, that might not have been what happened two weeks ago.
-------------------------------------------
Calculating Thor
Read 36 control systems and 958 targets.
Total connected: 32 Disconnected Controls
No backtracks, so only four attacks - there is an opportunity here to test if KB-O c6-3 is allowed for over-range attacks, though.
Another note here is that OG-E b12-2 should attack the spire system of OG-E b12-1: while this is within practicality to prevent, I suggest that we will learn more by allowing the attack to proceed to Alert.
-------------------------------------------
Calculating Raijin
Read 79 control systems and 915 targets.
Total connected: 79
Taranis, of course, goes out of bounds of what we can reasonably predict based on past behaviour.
Target
Target Distance
Control Distance
Attackers
Inhabited?
-
-
-
Control Sphere Edge
-
Worst case scenario within the scope of past behaviour: the initial auto-capture to 15 LY, invade to 20 LY attack is only guarded by an if (controls == 0) and can be - not very narratively - repeated.
Note that the prediction for HIP 7277 here is based on inhabited targets getting priority - HIP 8033 can also hit the more distant JN-K b8-3 (and nothing else can) so that might be targeted instead. With backtracks as they are, FG-Y d38 should also be skipped in favour of XJ-R b4-1 Edit: it's too early in the morning and I can't read my own tables properly
And Hadad is prevented from getting a second 12 LY Alert in a row
Target
Target Distance
Control Distance
Attackers
Inhabited?
Col 285 Sector SH-B b14-2
18.310
15.315
Col 285 Sector QM-B b14-1; Col 285 Sector QM-B b14-2;
No
Col 285 Sector KW-M c7-31
20.046
11.724
Col 285 Sector KW-M c7-7; Col 285 Sector KW-M c7-4; HIP 31648; etc
No
Col 285 Sector RM-B b14-8
20.607
15.317
Col 285 Sector RN-T d3-78; Col 285 Sector RM-B b14-3;
No
Col 285 Sector PM-B b14-3
20.783
14.577
HIP 31648; Col 285 Sector KW-M c7-5; Col 285 Sector KW-M c7-2; etc
No
Col 285 Sector PM-B b14-4
20.982
14.349
HIP 30502; Col 285 Sector KW-M c7-5; Col 285 Sector KW-M c7-2; etc
No
Col 285 Sector SH-B b14-7
21.723
15.882
Col 285 Sector WN-Z b14-0;
No
Col 285 Sector RM-B b14-4
21.892
15.344
HIP 31223; Col 285 Sector RM-B b14-3; Col 285 Sector VS-Z b14-3;
No
Col 285 Sector KW-M c7-28
22.158
17.550
Col 285 Sector KW-M c7-30;
No
Col 285 Sector WN-Z b14-2
22.372
18.869
Col 285 Sector WN-Z b14-1; Col 285 Sector SH-B b14-6;
No
Col 285 Sector SX-Z b14-2
22.853
17.346
Col 285 Sector US-Z b14-1; Col 285 Sector SX-Z b14-0;
Systems are listed in order of priority, and in general the first five would be expected to be hit by Alerts. Predictions made early in the week may be reissued later if Control recaptures materially affect them. If the Control Sphere Edge is reached and targeting mode switches, predictive confidence is lower and the consequences of recaptures may be more significant.
Table key
Name: Name of system considered at threat of Alert. Bold if in Control-based prioritisation it would be eligible for backtrack targeting. Distance: The distance in LY to the Maelstrom. A primary component of Thargoid prioritisation. Attackers: A list of potential Controls to launch the attack from, partial if there are 4 or more. Controls disconnected from their parent maelstrom are marked in italics; controls attacking a system closer to the maelstrom than themselves are underlined; controls which may be skipping an inner uninhabited system to strike an inhabited system further out are struck-through; controls containing a barnacle matrix are bold. Once targeting switches to Control-based rather than Target-based prioritisation, only one is listed here. Inhabited: Whether the system contains standing human population.
Taranis is for now not in scope for predictions. More information as it comes in...
-------------------------------------------
Calculating Leigong
Read 12 control systems and 982 targets.
Total connected: 9 Disconnected Controls
MX-U c2-19 is a spire recapture attempt. With no usable backtracks, the default case has Leigong running out of Alerts before it can place it - but that could easily change, of course.
-------------------------------------------
Calculating Indra
Read 48 control systems and 945 targets.
Total connected: 37 Disconnected Controls
Systems are listed in order of priority, and in general the first five would be expected to be hit by Alerts. Predictions made early in the week may be reissued later if Control recaptures materially affect them. If the Control Sphere Edge is reached and targeting mode switches, predictive confidence is lower and the consequences of recaptures may be more significant.
Table key
Target: Name of system considered at threat of Alert. Bold if in Control-based prioritisation it would be eligible for backtrack targeting. Target Distance: The distance in LY to the Maelstrom of the target. A primary component of Thargoid prioritisation. Control Distance: The distance in LY to the Maelstrom of the attacking Control. A primary component of Thargoid prioritisation when attacking outside the control sphere. Attackers: A list of potential Controls to launch the attack from, partial if there are 4 or more. Controls disconnected from their parent maelstrom are marked in italics; controls attacking a system closer to the maelstrom than themselves are underlined; controls which may be skipping an inner uninhabited system to strike an inhabited system further out are struck-through; controls containing a Spire are bold. Once targeting switches to Control-based rather than Target-based prioritisation, only one is listed here. Inhabited: Whether the system contains standing human population.
All predictions good last week. Back down to just four inhabited Alerts predicted for next week
-------------------------------------------
Calculating Leigong
Read 7 control systems and 990 targets.
Total connected: 3 Disconnected Controls
System
Distance
HIP 8033
9.279145384
Arietis Sector ZE-R b4-3
9.933224316
Arietis Sector XJ-R b4-0
14.45838587
HIP 10118
15.10286992
Furthest Control: 15.103 LY
Target
Target Distance
Control Distance
Attackers
Inhabited?
-
-
-
Control Sphere Edge
-
Hyades Sector JN-K b8-3
17.809
9.279
HIP 8033;
No
Arietis Sector WJ-R b4-3
22.236
14.417
HIP 9180; (backtrack Arietis Sector WJ-R b4-1)(backtrack Arietis Sector WJ-R b4-0)(backtrack HIP 9137)
No
Arietis Sector XJ-R b4-1
18.476
14.458
Arietis Sector XJ-R b4-0;
No
Arietis Sector KM-W c1-15
24.725
15.102
Arietis Sector YE-R b4-3 (9.945 LY);
No
Only four alerts possible, so whatever is available will be used
-------------------------------------------
Calculating Indra
Read 47 control systems and 946 targets.
Total connected: 35 Disconnected Controls
System
Distance
75 Tauri
12.76477392
HIP 19098
13.95811956
Arietis Sector IG-X b1-4
15.09711401
76 Tauri
15.46350921
Arietis Sector HG-X b1-1
15.84982009
Arietis Sector HG-X b1-2
15.8593673
HIP 21179
16.59951642
Hyades Sector NN-S b4-2
17.95964443
Hyades Sector NN-S b4-1
18.37212988
Hyades Sector JH-V c2-13
18.59377626
Hyades Sector PI-S b4-3
19.51369211
Lei Hsini
21.10781938
Furthest Control: 21.108 LY
Target
Target Distance
Control Distance
Attackers
Inhabited?
71 Tauri
15.082
9.009
HIP 20086 (9.925 LY); 63 Tauri; HIP 20350; etc
No
86 Rho Tauri
18.734
11.826
63 Tauri (9.973 LY); HIP 20916;
No
Hyadum II
18.976
12.724
HIP 20350; 64 Tauri; HIP 20916; etc
No
79 b Tauri
19.444
17.089
HIP 20916;
No
Arietis Sector JR-V b2-4
19.729
12.757
HIP 20349; HIP 20480;
No
77 Theta-1 Tauri
20.629
13.186
64 Tauri; HR 1354; HIP 20679;
No
70 Tauri
20.963
17.820
HR 1354; HIP 20679;
Yes
-
-
-
Control Sphere Edge
-
Arietis Sector LM-V b2-5
22.145
13.958
HIP 19098;
No
HIP 19157
21.650
15.097
Arietis Sector IG-X b1-4;
Yes
Hyades Sector PI-S b4-2
22.428
15.464
76 Tauri;
No
The edge gets slightly closer at Indra this week, but still not close enough.
-------------------------------------------
Calculating Oya
Read 24 control systems and 969 targets.
Total connected: 24
Usable backtrack so all five attacks should go through. Curiously, the first attack is an inside backtrack from HIP 8525, which might make for an interesting targeting shortage next week.
-------------------------------------------
Calculating Cocijo
Read 57 control systems and 937 targets.
Total connected: 56 Disconnected Controls
System
Distance
Col 285 Sector WY-F b12-1
20.85255624
Furthest Control: 21.999 LY
Target
Target Distance
Control Distance
Attackers
Inhabited?
Col 285 Sector ZE-P c6-15
18.409
9.869
Col 285 Sector OS-T d3-96; Mapon;
No
Col 285 Sector ZE-P c6-16
19.205
17.824
Mapon;
No
Col 285 Sector UN-H b11-3
19.395
13.304
Col 285 Sector SS-H b11-7; Col 285 Sector VY-Q c5-18;
No
Kurumanit
20.237
20.853
Col 285 Sector WY-F b12-1;
Yes
Col 285 Sector SS-H b11-5
20.306
12.899
Col 285 Sector SS-H b11-1; Col 285 Sector VY-Q c5-15; Col 285 Sector VY-Q c5-17; etc
No
Col 285 Sector ZT-F b12-8
21.247
16.728
Col 285 Sector ZT-F b12-3;
No
Col 285 Sector ZT-F b12-2
21.760
20.745
HIP 38235;
No
-
-
-
Control Sphere Edge
-
Col 285 Sector VN-H b11-5
24.181
14.622
Col 285 Sector VN-H b11-1; (backtrack Col 285 Sector VN-H b11-6)
No
Col 285 Sector OS-T d3-136
22.883
15.249
Col 285 Sector OS-T d3-92; (backtrack Col 285 Sector OS-T d3-69)
No
Col 285 Sector VN-H b11-6
22.723
15.670
HIP 36809;
No
Nothing out of the ordinary here
-------------------------------------------
Calculating Thor
Read 36 control systems and 958 targets.
Total connected: 32 Disconnected Controls
