Analysing the Thargoid Simulation

Narwhal Nose report generated 15 June

-------------------------------------------

Systems are listed in order of priority, and in general the first five would be expected to be hit by Alerts, with a variable number of reserve targets shown depending on confidence levels. Predictions made early in the week may be reissued later if Control recaptures materially affect them.

Table key
Name
: Name of system considered at threat of Alert.
Distance: The distance in LY to the Maelstrom. A primary component of Thargoid prioritisation.
Controls: The number of Controls which can theoretically attack this system this week.
Confidence: The confidence that any Control can attack this system this week. Numbers under 1 should be treated as increasingly unlikely, while numbers above 2 are almost certain within the constraints of the model.
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; these can still attack but are strategically interesting.
Inhabited: Whether the system contains standing human population.
Advance: The approximate direction of the Alert relative to the Maelstrom. +1=towards Sol, -1=away from Sol, 0=perpendicular to Sol

-------------------------------------------

Calculating Taranis
Read 119 control systems and 872 targets.
Total connected: 114
Disconnected Controls
SystemDistance
HIP 2567015.28147367
Trianguli Sector KR-W b1-118.60194147
Matshiru19.81269716
Hyades Sector IM-L b8-525.77177856
Trianguli Sector JW-W b1-626.91604787


TargetDistanceControlsConfidenceAttackersInhabited?Advance
HIP 2371618.43066Trianguli Sector BA-A d85; Trianguli Sector CA-A c22; Trianguli Sector FL-Y b4; etcYes0.9
Imeut19.13244HIP 25670; Hyades Sector FB-N b7-3; Trianguli Sector KR-W b1-1; etcYes0.8
Ebisu21.04966Hyades Sector BV-O b6-4; Hyades Sector EB-N b7-0; Hyades Sector GW-W d1-87 (10.024 LY); etcYes0.1
Cao Tzu21.51844Hyades Sector GW-W d1-87; Hyades Sector GW-W d1-86; Hyades Sector AV-O b6-4; etcYes-0
HIP 2627423.64222Hyades Sector GW-W d1-81; Hyades Sector ZZ-O b6-1;Yes0.1
Hyades Sector AV-O b6-523.97522Hyades Sector AV-O b6-4; Hyades Sector GW-W d1-76;Yes-0.1
HIP 2199125.78611Trianguli Sector JR-W b1-5 (9.904 LY);Yes0.4
Ge27.68333Haushu; Hyades Sector ZZ-O b6-1; Hyades Sector ZZ-O b6-2;Yes0.2
HIP 2692628.17022Hyades Sector ZZ-O b6-1; Hyades Sector ZZ-O b6-2;Yes0.3
Trianguli Sector JW-W b1-128.92222Hyades Sector IM-L b8-5; Trianguli Sector JW-W b1-6; No0.6
Hyades Sector YZ-O b6-328.96922Trianguli Sector ZJ-A b1; Hyades Sector YZ-O b6-0;Yes0.2
Hyades Sector EG-N b7-529.05822Hyades Sector EG-N b7-3; Hyades Sector EG-N b7-4;No0.3
Hyades Sector EQ-O b6-429.07233Hyades Sector EQ-O b6-2; Hyades Sector DQ-O b6-2; Hyades Sector DQ-O b6-4;No-0.9
Hyades Sector XO-Q b5-429.26433Hyades Sector GW-W d1-82; Hyades Sector XO-Q b5-3; HIP 25388;No-0.5
28 additional targets not listed, 42 total
Five strongly connected inhabited systems at the top, so those should be pretty safe

-------------------------------------------

Calculating Leigong
Read 164 control systems and 831 targets.
Total connected: 158
Disconnected Controls
SystemDistance
HIP 1005621.76223165
Hyades Sector LN-K b8-325.22509988
Hyades Sector LN-K b8-425.70606461
Hyades Sector LN-K b8-226.37692529
Arietis Sector CQ-P b5-229.48322815
Arietis Sector CQ-P b5-134.62892013


TargetDistanceControlsConfidenceAttackersInhabited?Advance
HIP 1092124.88622Arietis Sector VO-R b4-2; Arietis Sector VO-R b4-3;No0.4
Arietis Sector YU-P b5-025.20311Arietis Sector AQ-P b5-2;No0.5
Arietis Sector NX-U c2-1227.42411Arietis Sector KM-W d1-93;No0.9
Arietis Sector EW-N b6-228.33911Arietis Sector EW-N b6-1;No0.8
Arietis Sector UO-R b4-430.97111Arietis Sector VO-R b4-3;No0.6
Arietis Sector DW-N b6-338.31722HIP 6380; HIP 6869;No0.5
Arietis Sector ZU-P b5-038.33533Arietis Sector ZU-P b5-4; Arietis Sector VO-R b4-0; Arietis Sector ZU-P b5-2;No0.8
HIP 1071040.02711Arietis Sector FG-Y d68;No-0.2
Hyades Sector CB-O b6-040.52422Hyades Sector CB-O b6-1; HIP 11309;No-0.8
Arietis Sector SD-T b3-040.75511Arietis Sector FG-Y d49;No-0.6
Hyades Sector KX-U d2-4940.89011HIP 5685;No0.3
Matsucha41.28522Arietis Sector VO-R b4-0; Arietis Sector ZU-P b5-2;Yes0.9
HIP 520741.30911Col 285 Sector DG-O c6-16;No0
HIP 566241.41111HIP 6001;No-0.4
Col 285 Sector GM-C b13-241.62411Hyades Sector MT-I b9-1;No-0.1
Bamarakw42.09911Arietis Sector ZU-P b5-2;Yes0.9
Arietis Sector GG-Y d6842.34911HIP 11309;No-0.6
Arietis Sector QS-U b2-344.03922Arietis Sector QS-U b2-2; Arietis Sector EL-Y c8;No-0.6
4 additional targets not listed, 22 total
Nothing inhabited near the top. Jumping all the way down to Matsucha is possible but it's 10 LY further out than the 5th on the list so that would get us quite a bit of info if so.

-------------------------------------------

Calculating Indra
Read 155 control systems and 839 targets.
Total connected: 155

TargetDistanceControlsConfidenceAttackersInhabited?Advance
HIP 2089021.889141464 Tauri (10.013 LY); HIP 20577; HIP 20679; etcYes0.9
Kagutsuchi22.49622Arietis Sector LM-V b2-3; Arietis Sector NH-V b2-0;Yes-0.4
HIP 2089923.086232371 Tauri; HIP 20916; HIP 20577; etcYes1
HIP 2049224.0432222HIP 20916; HIP 20577; 86 Rho Tauri; etcYes1
HIP 2001925.5831919HIP 20577; HIP 20679; Hyadum II; etcYes1
Arietis Sector DQ-Y c1826.58944Arietis Sector HG-X b1-3; Arietis Sector HG-X b1-4; Arietis Sector DQ-Y c9; etcYes-0.4
HIP 2085026.986141477 Theta-1 Tauri; 70 Tauri; HIP 20815; etcYes0.9
Hyades Sector LC-U b3-327.51244Hyades Sector NN-S b4-0 (9.980 LY); Hyades Sector LC-U b3-4; Hyades Sector FB-X c1-17; etcNo-1
Hyades Sector VK-L a9-027.65066Hyades Sector NN-S b4-4; Hyades Sector AR-J a10-0; HIP 21788; etcNo-0.3
HIP 2082627.6826679 b Tauri; HR 1358; HIP 20616; etcYes0.9
HIP 2071927.7171515Hyadum II; 70 Tauri; HIP 20815; etcYes1
HIP 2145927.73233Arietis Sector TY-P a6-0; Arietis Sector TY-P a6-1; Arietis Sector TY-P a6-2;Yes0.7
Hyades Sector JD-G a12-027.76333HIP 22496; HIP 22422; HIP 22203;No0.6
89 Tauri27.775121270 Tauri; HIP 20815; 92 Sigma-2 Tauri; etcNo0.9
69 additional targets not listed, 83 total
Lots of inhabited systems at the top, so this is likely to come through normally

-------------------------------------------

Calculating Oya
Read 52 control systems and 940 targets.
Total connected: 37
Disconnected Controls
SystemDistance
Chernobo15.57607967
Cephei Sector BV-Y b215.98888774
Tougeir16.22455941
Liu Huang17.75687587
Lyncis Sector YF-O b6-218.02935432
Akbakara18.17006789
HR 110718.24317616
HIP 2432918.93453463
Muchihiks19.56140173
HIP 882519.96312519
HIP 2138620.50900145
Lyncis Sector TZ-P b5-120.5449916
Cephei Sector CV-Y b122.03949314
Lyncis Sector YF-O b6-122.22951568
Jeng23.03807565


TargetDistanceControlsConfidenceAttackersInhabited?Advance
HIP 691320.35911HR 1107; Yes-0
Luggerates21.96233Sambaho; Cephei Sector FB-X b1-1; Cephei Sector EB-X b1-4;Yes0.3
MCC 10522.32211HIP 21386; Yes0.9
Aowicha23.76911Daruwach;Yes-0.3
Poqomathi24.13633Cephei Sector DQ-Y b1; HIP 8525; HIP 7338 (10.020 LY);Yes0.6
Cephei Sector AV-Y b424.97511Cephei Sector AV-Y b6;No-0.2
Gliese 305025.57922HIP 8525; HIP 7338;No0.6
Gliese 984326.60722Cephei Sector FB-X b1-1; Cephei Sector EB-X b1-4;No0.4
HIP 3822526.95611Lyncis Sector YF-O b6-1; Yes-0.3
Cephei Sector AV-Y b526.96411Cephei Sector EB-X b1-4;No-0.1
SPOCS 28027.39511Cephei Sector CV-Y b1; No0.9
Cephei Sector ZE-A c1228.09311Cephei Sector AV-Y b0;No-0.4
Cephei Sector HW-W b1-528.30611BD+77 84;No0.9
Lyncis Sector XU-P b5-128.40911Jeng; No0.4
Cephei Sector DQ-Y b428.49611HIP 11111;No0.7
Yemaki28.83411Cephei Sector AF-A c22;Yes0.3
Nawad29.01811Cephei Sector AF-A c21;Yes0.7
No further targets possible
Top five are all inhabited, but will Oya place a full five or just four, and will it do a Hadad/Thor-style "further out" run? There's also a few opportunities here for recaptures on disconnected branches to permanently clear things up.

-------------------------------------------

Calculating Cocijo
Read 203 control systems and 790 targets.
Total connected: 203

TargetDistanceControlsConfidenceAttackersInhabited?Advance
Col 285 Sector YT-F b12-723.87811Col 285 Sector YT-F b12-2;No0.7
Laumas29.26988Col 285 Sector SS-H b11-0; Col 285 Sector SS-H b11-3; Col 285 Sector SS-H b11-2; etcYes0.5
Col 285 Sector YT-F b12-529.60522Col 285 Sector YT-F b12-1; Col 285 Sector OS-T d3-102;No0.8
Col 285 Sector BA-P c6-329.64344Col 285 Sector YT-F b12-6; HR 3048; Chibis; etcNo1
Col 285 Sector YT-F b12-330.01422Col 285 Sector YT-F b12-4; Col 285 Sector OS-T d3-102;Yes0.9
Col 285 Sector AP-F b12-230.06711Col 285 Sector YT-F b12-0;No0.7
Col 285 Sector AF-P c6-1630.96544Col 285 Sector YY-F b12-0; Col 285 Sector AF-P c6-17; Col 285 Sector YY-F b12-3; etcNo-0.6
Col 285 Sector BA-P c6-830.99233Njana; Col 285 Sector DA-E b13-8; Col 285 Sector DA-E b13-3;No0.4
Col 285 Sector YY-F b12-531.44433Col 285 Sector AF-P c6-17; Col 285 Sector YY-F b12-3; Col 285 Sector YY-F b12-6;No-0.5
Col 285 Sector YY-F b12-431.52977Col 285 Sector AU-F b12-2; Col 285 Sector AU-F b12-4; Col 285 Sector YY-F b12-3; etcNo-0.5
Col 285 Sector YT-Q c5-1131.56355Col 285 Sector YT-Q c5-12; Col 285 Sector YT-Q c5-14; Col 285 Sector YT-Q c5-10; etcNo-0.9
Col 285 Sector YT-Q c5-2331.58444Col 285 Sector VN-H b11-2; Col 285 Sector WN-H b11-5; Col 285 Sector YT-Q c5-25; etcNo-0.9
Col 285 Sector YY-F b12-131.58644Col 285 Sector AU-F b12-4; Col 285 Sector YY-F b12-3; Col 285 Sector YY-F b12-6; etcNo-0.4
Col 285 Sector UN-H b11-031.61411HIP 35633;No0.3
Col 285 Sector ZE-P c6-431.64111Col 285 Sector BF-E b13-1;No0.3
58 additional targets not listed, 73 total
Not much inhabited in the top 5 ... but nothing on the immediate reserve list either. Not impossible that it could target inhabited systems further down the list, though.

-------------------------------------------

Calculating Thor
Read 134 control systems and 863 targets.
Total connected: 116
Disconnected Controls
SystemDistance
Rajuarpai11.4695589
Chanyaya16.10879151
HIP 1989416.20887223
Col 285 Sector IG-O c6-1417.71585625
HIP 2002419.46077284
Col 285 Sector SM-C b13-021.77609336
Col 285 Sector UH-C b13-121.81126877
Col 285 Sector UH-C b13-022.79575584
Col 285 Sector SM-C b13-123.95464872
HIP 1885724.61621433
Col 285 Sector JG-O c6-524.84190245
Col 285 Sector SM-C b13-225.94627111
Col 285 Sector SM-C b13-326.05759096
Col 285 Sector HL-O c6-430.23485545
Col 285 Sector HL-O c6-531.49809332
Col 285 Sector HL-O c6-331.52685177
Col 285 Sector ML-E b12-535.7163303
Col 285 Sector DF-Q c5-442.75242135


TargetDistanceControlsConfidenceAttackersInhabited?Advance
Unktety25.35711HIP 19198;Yes1
HIP 1695432.67111HIP 17897;Yes0.4
Col 285 Sector DF-Q c5-1841.00211Col 285 Sector DF-Q c5-4; No0.2
HIP 2215944.43222Col 285 Sector HF-G b11-3; Col 285 Sector CF-Q c5-17;No0.2
Synuefe QO-Q c21-544.85411Synuefe QO-Q c21-1;No-0.7
Col 285 Sector OL-F b11-245.30111Col 285 Sector NQ-F b11-2;No-0.6
HIP 2263245.36411Col 285 Sector CF-Q c5-17 (10.022 LY);No0.4
No further targets possible
Thor's previous disaster week has left it with very few places to launch Alerts from this week either. There's a little uncertainty over which Controls were used last week but it doesn't appear to be affecting the prediction either way.

-------------------------------------------

Calculating Raijin
Read 172 control systems and 823 targets.
Total connected: 172

TargetDistanceControlsConfidenceAttackersInhabited?Advance
HIP 11636020.90222Pegasi Sector IH-U b3-0; Pegasi Sector BQ-Y d71;Yes-0.5
Holvandalla21.4761010Pegasi Sector NN-S b4-10; Kaurukat; Humarala; etcYes0.6
Isla23.90055Pegasi Sector LC-U b3-2 (9.952 LY); HIP 116542; Wanmi; etcYes-0.1
Kuruma25.52422Pegasi Sector DG-X c1-6; Tagin;Yes0.2
Koko Oh27.0661212HIP 113535; Vistnero; Pegasi Sector MY-O a7-5; etcYes0.6
Pegasi Sector FW-W d1-10427.20911Pegasi Sector OI-S b4-6;No-0.7
Pegasi Sector WK-L a9-327.26644Pegasi Sector NN-S b4-4; Pegasi Sector RE-N a8-0; Pegasi Sector RE-N a8-4; etcNo0.9
Pegasi Sector VK-L a9-127.39266Pegasi Sector UK-L a9-3; Pegasi Sector ZQ-J a10-1; Ixbaksha; etcNo0.7
Pegasi Sector PE-N a8-127.4191111Pegasi Sector DG-X c1-4; Pegasi Sector PE-N a8-3; Pegasi Sector PE-N a8-2; etcNo-0.3
Pegasi Sector ON-S b4-227.46211HIP 113076;No1
Pegasi Sector JS-Q a6-227.53188Pegasi Sector NY-O a7-1; Tagin; Pegasi Sector EB-W b2-2; etcNo0.4
Pegasi Sector KC-U b3-127.54766Pegasi Sector KC-U b3-2; Pegasi Sector BQ-Y d93; Pegasi Sector BQ-Y d71; etcNo-0.8
Pegasi Sector KH-V c2-2527.61622Pegasi Sector OI-S b4-4 (9.980 LY); Pegasi Sector KH-V c2-13;No0.1
Pegasi Sector OY-O a7-027.67066Pegasi Sector JH-U b3-9; Tagin; Pegasi Sector NY-O a7-5; etcNo0.6
86 additional targets not listed, 100 total
With five inhabited systems at the top of the list, it'll probably do just that.

-------------------------------------------

Calculating Hadad
Read 91 control systems and 907 targets.
Total connected: 89
Disconnected Controls
SystemDistance
Col 285 Sector TH-B b14-526.54576679
Col 285 Sector TH-B b14-426.61885566


TargetDistanceControlsConfidenceAttackersInhabited?Advance
HIP 2959618.22522Montioch; HR 2204;Yes0.8
Muruidooges18.36733Col 285 Sector RH-B b14-2 (9.934 LY); Omumba; HR 2204;Yes0.6
Fotlandjera19.68711Omumba;Yes0.2
Col 285 Sector SX-Z b14-222.85333Col 285 Sector US-Z b14-1; Col 285 Sector SX-Z b14-0; Col 285 Sector OR-B b14-4;No0.3
Col 285 Sector GQ-O c6-1926.98422Col 285 Sector SH-B b14-2; Col 285 Sector GQ-O c6-22;No-0.8
Col 285 Sector OB-D b13-428.17511Col 285 Sector GQ-O c6-22;No-0.5
Col 285 Sector OM-B b14-729.57311Col 285 Sector JW-M c7-11;No0.8
Col 285 Sector ZY-X b15-830.30711Col 285 Sector VS-Z b14-5;No-0.3
Col 285 Sector XN-Z b14-631.83722Col 285 Sector VS-Z b14-1; Col 285 Sector KW-M c7-17;No-0.7
Col 285 Sector RN-T d3-8432.47911Col 285 Sector KW-M c7-17;No-0.7
Col 285 Sector TH-B b14-633.22111Col 285 Sector TH-B b14-5; No-1
No further targets possible
Also a relatively short list of possible Alert targets in total here, where the main reason to believe that it won't be the top 5 is that Hadad start-of-week predictions always need revising mid-week anyway.

And new from now on ... here's the list of controls presumed exhausted. Format is "system name : probability of exhaustion", probability should usually be 1 but as noted above there's a little uncertainty in Thor this week.
Code:
-- Taranis
Matshiru:1
Hyades Sector DQ-O b6-3:1
Trianguli Sector EQ-Y b5:1
Trianguli Sector FG-Y d96:1
Hyades Sector NS-T c3-14:1
-- Leigong
Jementi:1
Arietis Sector CQ-P b5-2:1
Arietis Sector CQ-P b5-1:1
Arietis Sector VO-R b4-4:1
Arietis Sector JM-W d1-83:1
-- Indra
63 Tauri:1
HR 1354:1
HIP 20712:1
Arietis Sector JR-V b2-4:1
Arietis Sector JR-V b2-1:1
-- Oya
Chernobo:1
Tougeir:1
HIP 10778:1
Cephei Sector FB-X b1-0:1
-- Cocijo
Mapon:1
Col 285 Sector WY-F b12-3:1
Col 285 Sector SS-H b11-5:1
Kurumanit:1
Col 285 Sector WY-F b12-5:1
-- Thor
Col 285 Sector FU-H b10-2:1
---- not sure precisely, so go half-and-half on each
Col 285 Sector FU-H b10-3:0.5
HIP 20807:0.5
-- Raijin
Pegasi Sector PI-S b4-0:1
Pegasi Sector HH-U b3-4:1
Pegasi Sector JH-U b3-8:1
Pegasi Sector DG-X c1-5:1
Pegasi Sector VK-L a9-0:1
-- Hadad
Col 285 Sector VN-Z b14-0:1
Col 285 Sector RH-B b14-5:1
 
Huh. If enough of the right systems are cleared at Hadad, it may actually be possible to stop it having enough eligible targets to place five Alerts.
 
Indra: 60%. HIP 20890 and HIP 20899 went to four weeks, but Kagutsuchi didn't and was still skipped. Then we get Arietis Sector DQ-Y c18 (uninhabited, backwards) skipped in favour of HIP 21380 (inhabited, forwards) for the second mistake - which was somewhat expected but not yet part of the model.
Noticed something while giving INTRA the attackers/targets for this cycle and checking against your comments about what got skipped!
Arietis Sector DQ-Y c18 is actually inhabited (and been invaded a couple times) but unlike the other places it has no orbital outposts/starports, only planetary.
The "unpopulated = extra distance" idea could still work but maybe Tharg's definition is actually "no orbitals" (so unpopulated meets that automatically).
Could also have multiple levels with different missing port types adding more virtual distance.

It seems uncontroversial to suggest that the Thargoids now won't attack a system in its fourth recovery week, even if that week is spent in "safe" state due to repairs to surface bases.
This rule works really well!
After adding it and refreshing the cycle 28 targets it removed all the ones you asterisked and only improved the whole thing.
I reckon the damaged recovery was always meant to be like that - you get 4 weeks alien-free, but actually finishing it leaves everything open for business again.

I got rid of all query logic based on recovery states, rewrote it purely to use the non-recovery parts of your cooldown image, then changed damage invasions from 3 to 4.
Basically alerts and no-damage invasions are 2, damage invasions and controls are 4, recovery can be ignored.
with a as (select addr,war,prog,prog_eddn from act where cycle=?1 and (?2 or addr not in (select addr_x from attack where cycle=?1))),
a_addr as (select addr from act join sys using(addr) where cycle<=?1 and war!='R' and (cycle=?1 or (not ?3 and prog>=100 and cycle>?1-case when war='A' then 2 when war='I' then (case when act.ports<sys.ports then 4 else 2 end) when war='C' then 4 end)))
select m.addr maddr, m.name mname,
x.addr xaddr, x.name xname, x.mael_d xdist, x.inhab xpop,
y.addr yaddr, y.name yname, y.mael_d ydist, y.inhab ypop
from a
join s.sys x using(addr)
join s.mael m on x.mael_addr=m.addr
join s.sys ms on ms.addr=m.addr
left join near n on x.addr in (n.addr_a, n.addr_b)
join s.sys y on y.addr in (n.addr_a, n.addr_b) and y.addr not in (x.addr, y.mael_addr) and y.addr not in a_addr
where a.war='C' and a.prog<100 and a.prog_eddn<1.0
order by ms.x desc, y.mael_d asc, x.mael_d asc

Adding a group by and an aggregate gives Narwhal Nose but I handled that elsewhere for display reasons.
Finding the cooldown could be cleaned up a bit because it has multiple code paths for 2 and 4, but for now it's nice to keep an easy way to change it for different states.

Huh. If enough of the right systems are cleared at Hadad, it may actually be possible to stop it having enough eligible targets to place five Alerts.
Bit more than maybe, we did that last cycle and now it only attacked 2 systems.
Same at Thor - that would have been 0 but we left one for science.
 
Right, I think I got this cycle's attacks added.
This should update itself as we get new scan or EDDN data - https://dev.iniv.space/targets/29 + ping @deanom59

I undid FU-H b10-3 attacking OC-V d2-75 at Thor last cycle (28), so now that flags up a warning.
Those targets match what we can see on the map this cycle (29) though, so I assumed FU-H b10-2 attacked OC-V d2-73 and FU-H b10-3 attacked FU-H b10-4.
Looking at it I think the only differences now are where Narwhal Nose has >10 LY adjacency cases.
Do we know any upper/lower limits for that, or know if there are cases where 10.02 did attack but 10.01 did not?
 
or know if there are cases where 10.02 did attack but 10.01 did not?
Yes, unfortunately. Col 285 Sector TS-H b11-5 didn't attack Col 285 Sector VY-Q c5-9 (10.00 LY but above 10 at the third decimal place) ... but Arietis Sector GG-Y d63 may have been attacked from HIP 10921 at a distance of 10.013 LY and I think there was a much earlier example in the 10.01-10.02 distance range as well.

I haven't been able to reverse-engineer a rounding algorithm to make that work without also ruling out other attacks we know happened below 10 LY, and it's so rare that I think just using a strict 10 as the distance is probably fine in general - there's been exactly one exception to it while NN has been running.

Arietis Sector DQ-Y c18 is actually inhabited
It is - I've even got it recorded as inhabited, too.

I am wondering - since there was also a swap between two uninhabited systems at Indra last week in similar circumstances, and Oya skipped HIP 38225 in favour of Orong and Benanekpeno - if there's also a slight prioritisation of advancing towards the bubble rather than towards open space been added too. There don't appear to be any likely tests of this coming up this week, though.


Great work on getting the live calculations up - that should be a lot less to do during the week.
 
Prediction changes as a result of recaptures: (Leigong edited due to further recaptures)
Taranis: minor changes in detail only, no change to predicted targets

Leigong:
TargetDistanceControlsConfidenceAttackersInhabited?Advance
Arietis Sector YU-P b5-025.20311Arietis Sector AQ-P b5-2; No0.5
Arietis Sector NX-U c2-1227.42411Arietis Sector KM-W d1-93; No0.9
Arietis Sector EW-N b6-228.33911Arietis Sector EW-N b6-1; No0.8
Arietis Sector DW-N b6-338.31722HIP 6380; HIP 6869; No0.5
Hyades Sector KX-U d2-4940.89011HIP 5685; No0.3
HIP 520741.30911Col 285 Sector DG-O c6-16; No0
HIP 566241.41111HIP 6001; No-0.4
Col 285 Sector GM-C b13-241.62411Hyades Sector MT-I b9-1; No-0.1
Ceti Sector DB-X b1-448.05911HIP 6679 (9.904 LY); No0.7
Ceti Sector DB-X b1-049.49011Ceti Sector DB-X b1-2; No0.7
No further targets possible
Substantial reduction of the target list and several changes in the top 5

Indra: no changes, even if HIP 20056 was completed there'd only be minor implications

Oya:
TargetDistanceControlsConfidenceAttackersInhabited?Advance
Luggerates21.96211Sambaho;Yes0.3
Aowicha23.76911Daruwach;Yes-0.3
Poqomathi24.13633Cephei Sector DQ-Y b1; HIP 8525; HIP 7338 (10.020 LY);Yes0.6
Gliese 305025.57922HIP 8525; HIP 7338;No0.6
Cephei Sector HW-W b1-528.30611BD+77 84;No0.9
Nawad29.01811Cephei Sector AF-A c21;Yes0.7
No further targets possible
Target list trimmed considerably, possibility of jump to Nawad

Cocijo: substantial number of recaptures but it doesn't change the targeting list. Chibis isn't critical to this week's attacks either.

Thor:
TargetDistanceControlsConfidenceAttackersInhabited?Advance
Unktety25.35711HIP 19198;Yes1
No further targets possible
The pushback continues

Raijin:
TargetDistanceControlsConfidenceAttackersInhabited?Advance
HIP 11636020.90222Pegasi Sector IH-U b3-0; Pegasi Sector BQ-Y d71;Yes-0.5
Holvandalla21.4761010Pegasi Sector NN-S b4-10; Kaurukat; Humarala; etcYes0.6
Isla23.90055Pegasi Sector LC-U b3-2 (9.952 LY); HIP 116542; Wanmi; etcYes-0.1
Koko Oh27.0661212HIP 113535; Vistnero; Pegasi Sector MY-O a7-5; etcYes0.6
Pegasi Sector FW-W d1-10427.20911Pegasi Sector OI-S b4-6;No-0.7
Pegasi Sector WK-L a9-327.26644Pegasi Sector NN-S b4-4; Pegasi Sector RE-N a8-0; Pegasi Sector RE-N a8-4; etcNo0.9
Pegasi Sector VK-L a9-127.39266Pegasi Sector UK-L a9-3; Pegasi Sector ZQ-J a10-1; Ixbaksha; etcNo0.7
Pegasi Sector PE-N a8-127.4191111Pegasi Sector DG-X c1-4; Pegasi Sector PE-N a8-3; Pegasi Sector PE-N a8-2; etcNo-0.3
Pegasi Sector ON-S b4-227.46211HIP 113076;No1
Pegasi Sector JS-Q a6-227.53177Pegasi Sector NY-O a7-1; Pegasi Sector EB-W b2-2; Pegasi Sector NY-O a7-5; etcNo0.4
Pegasi Sector KC-U b3-127.54766Pegasi Sector KC-U b3-2; Pegasi Sector BQ-Y d93; Pegasi Sector BQ-Y d71; etcNo-0.8
Pegasi Sector KH-V c2-2527.61622Pegasi Sector OI-S b4-4 (9.980 LY); Pegasi Sector KH-V c2-13;No0.1
Pegasi Sector OY-O a7-027.67055Pegasi Sector JH-U b3-9; Pegasi Sector NY-O a7-5; Pegasi Sector NY-O a7-2; etcNo0.6
Pegasi Sector SP-L a9-127.8171111Chakma; Pegasi Sector UK-L a9-5; Pegasi Sector UK-L a9-1; etcNo0.3
85 additional targets not listed, 99 total
Kuruma is safe, minor changes to the details but not the order as a result elsewhere

Hadad:
TargetDistanceControlsConfidenceAttackersInhabited?Advance
HIP 2959618.22522Montioch; HR 2204;Yes0.8
Muruidooges18.36733Col 285 Sector RH-B b14-2 (9.934 LY); Omumba; HR 2204;Yes0.6
Fotlandjera19.68711Omumba;Yes0.2
Col 285 Sector SX-Z b14-222.85333Col 285 Sector US-Z b14-1; Col 285 Sector SX-Z b14-0; Col 285 Sector OR-B b14-4;No0.3
No further targets possible
Again, substantially trimmed back.
 
Last edited:
Prediction accuracy - after accounting for the late Leigong recaptures - 100% on priority order at all Maelstroms.
Expected number of Alerts at 7 of the 8; Oya again skips placing its fifth Alert for unclear reasons.
 
Narwhal Nose report generated 22 June

-------------------------------------------

Systems are listed in order of priority, and in general the first five would be expected to be hit by Alerts, with a variable number of reserve targets shown depending on confidence levels. Predictions made early in the week may be reissued later if Control recaptures materially affect them.

Table key
Name
: Name of system considered at threat of Alert.
Distance: The distance in LY to the Maelstrom. A primary component of Thargoid prioritisation.
Controls: The number of Controls which can theoretically attack this system this week.
Confidence: The confidence that any Control can attack this system this week. Numbers under 1 should be treated as increasingly unlikely, while numbers above 2 are almost certain within the constraints of the model.
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; these can still attack but are strategically interesting.
Inhabited: Whether the system contains standing human population.
Advance: The approximate direction of the Alert relative to the Maelstrom. +1=towards Sol, -1=away from Sol, 0=perpendicular to Sol

-------------------------------------------

Calculating Taranis
Read 118 control systems and 872 targets.
Total connected: 113
Disconnected Controls
SystemDistance
HIP 2567015.28147367
Trianguli Sector KR-W b1-118.60194147
Matshiru19.81269716
Hyades Sector IM-L b8-525.77177856
Trianguli Sector JW-W b1-626.91604787


TargetDistanceControlsConfidenceAttackersInhabited?Advance
63 Eridani19.56211Hyades Sector PN-T c3-9;Yes-0.3
Senocidi20.26433Hyades Sector PN-T c3-8; HIP 24076; Hyades Sector LH-V c2-6;Yes-0.4
Nihal21.44144Trianguli Sector KR-W b1-1; Matshiru; Hyades Sector KH-L b8-0; etcYes0.4
HIP 2668821.93633Matshiru; Hyades Sector IM-L b8-5; Trianguli Sector JW-W b1-6; Yes0.4
Awara21.99744Hyades Sector EB-N b7-0; HIP 23593; Hyades Sector GW-W d1-86; etcYes0.4
Hyades Sector AV-O b6-523.97522Hyades Sector AV-O b6-4; Hyades Sector GW-W d1-76;Yes-0.1
HIP 2199125.78611Trianguli Sector JR-W b1-5 (9.904 LY);Yes0.4
Paeni26.7283329 e Orionis; Trianguli Sector ZJ-A b1; Hyades Sector YZ-O b6-0;Yes0.3
Ge27.68344Hyades Sector NS-T c3-14; Haushu; Hyades Sector ZZ-O b6-1; etcYes0.2
HIP 2692628.17033Haushu; Hyades Sector ZZ-O b6-1; Hyades Sector ZZ-O b6-2;Yes0.3
Trianguli Sector JW-W b1-128.92222Hyades Sector IM-L b8-5; Trianguli Sector JW-W b1-6; No0.6
Hyades Sector YZ-O b6-328.96922Trianguli Sector ZJ-A b1; Hyades Sector YZ-O b6-0;Yes0.2
Hyades Sector EG-N b7-529.05822Hyades Sector EG-N b7-3; Hyades Sector EG-N b7-4;No0.3
Hyades Sector EQ-O b6-429.07233Hyades Sector EQ-O b6-2; Hyades Sector DQ-O b6-2; Hyades Sector DQ-O b6-4;No-0.9
27 additional targets not listed, 41 total
Lots of high-connectivity inhabited systems at the top of the list. Some scope - though probably not in a single week - for retaking the disconnected Matshiru cluster.

-------------------------------------------

Calculating Leigong
Read 151 control systems and 843 targets.
Total connected: 143
Disconnected Controls
SystemDistance
HIP 1005621.76223165
Hyades Sector LN-K b8-325.22509988
Hyades Sector LN-K b8-425.70606461
Hyades Sector LN-K b8-226.37692529
Arietis Sector CQ-P b5-229.48322815
Arietis Sector VO-R b4-133.13603884
Arietis Sector CQ-P b5-134.62892013
Arietis Sector VO-R b4-436.02875642


TargetDistanceControlsConfidenceAttackersInhabited?Advance
Arietis Sector AQ-P b5-317.21411Arietis Sector FG-Y d66;No0.4
Pathamon22.06466HIP 7277; Arietis Sector JM-W d1-56; Arietis Sector MX-U c2-17; etcYes0.5
HIP 1061628.36022Arietis Sector CQ-P b5-2; Arietis Sector CQ-P b5-1; No0.7
Wolf 12128.91744HIP 10056; Hyades Sector LN-K b8-3; Hyades Sector LN-K b8-4; etcYes0.5
HIP 1113428.92811HIP 11137;No0.2
Arietis Sector YJ-R b4-335.37411Arietis Sector CQ-P b5-1; No0.6
HIP 520741.30911Col 285 Sector DG-O c6-16;No0
HIP 566241.41111HIP 6001;No-0.4
Col 285 Sector GM-C b13-241.62411Hyades Sector MT-I b9-1;No-0.1
Ceti Sector DB-X b1-448.05911HIP 6679 (9.904 LY);No0.7
Ceti Sector DB-X b1-049.49011Ceti Sector DB-X b1-2;No0.7
No further targets possible
A fairly short list here, and a couple of disconnected branches in the top 5 attackers.

-------------------------------------------

Calculating Indra
Read 155 control systems and 840 targets.
Total connected: 155

TargetDistanceControlsConfidenceAttackersInhabited?Advance
HIP 1915721.65011Arietis Sector IG-X b1-4;Yes-0.6
HIP 2052722.5402020Hyadum I; HIP 20397; 86 Rho Tauri; etcYes0.9
HIP 2049123.34188HIP 19934 (10.022 LY); HIP 20480; HIP 20712; etcYes0.4
HIP 1975724.52044HIP 20419; Scythia; Hyades Sector TO-Q b5-2; etcYes0.1
Arietis Sector JR-V b2-226.28677HIP 20480 (9.966 LY); HIP 20712; Arietis Sector JR-V b2-4; etcNo0.6
Arietis Sector DQ-Y c1826.58944Arietis Sector HG-X b1-3; Arietis Sector HG-X b1-4; Arietis Sector DQ-Y c9; etcYes-0.4
HIP 2085026.986141477 Theta-1 Tauri; 70 Tauri; HIP 20815; etcYes0.9
HIP 2147427.124121286 Rho Tauri; 70 Tauri; HIP 20815; etcYes1
48 Tauri27.453141470 Tauri; HIP 20815; HR 1358; etcYes1
Hyades Sector LC-U b3-327.51244Hyades Sector NN-S b4-0 (9.980 LY); Hyades Sector LC-U b3-4; Hyades Sector FB-X c1-17; etcNo-1
HIP 2131727.5151212HIP 20815; 92 Sigma-2 Tauri; HIP 20948; etcNo1
Hyades Sector VK-L a9-027.65066Hyades Sector NN-S b4-4; Hyades Sector AR-J a10-0; HIP 21788; etcNo-0.3
HIP 2082627.6826679 b Tauri; HR 1358; HIP 20616; etcYes0.9
HIP 2071927.7171313Hyadum II; 58 Tauri; 55 Tauri; etcYes1
70 additional targets not listed, 84 total
Given changes in behaviour in previous weeks, Arietis Sector JR-V b2-2 is not high confidence - a skip ahead to DQ-Y c18 or perhaps more likely HIP 20850 is very possible.

-------------------------------------------

Calculating Oya
Read 41 control systems and 951 targets.
Total connected: 31
Disconnected Controls
SystemDistance
Chernobo15.57607967
Cephei Sector BV-Y b215.98888774
Tougeir16.22455941
Liu Huang17.75687587
Lyncis Sector YF-O b6-218.02935432
Akbakara18.17006789
HIP 2432918.93453463
Muchihiks19.56140173
HIP 882519.96312519
Lyncis Sector TZ-P b5-120.5449916


TargetDistanceControlsConfidenceAttackersInhabited?Advance
Cephei Sector DQ-Y b222.14911HIP 7338 (9.988 LY);No0.5
Col 285 Sector HD-G b12-122.75311Cephei Sector WO-A b4;No-0.9
Muncheim23.55711Cephei Sector FB-X b1-1;Yes0.7
Cephei Sector HW-W b1-528.30611BD+77 84;No0.9
Nawad29.01811Cephei Sector AF-A c21;Yes0.7
No further targets possible
Starting the week with just five targets, and more importantly with only five perimeter controls available to attack at all, a zero-Alert week isn't impossible here. Oya has only placed four Alerts twice in a row so it might not hit all five even if left completely alone ... not that this is likely!

-------------------------------------------

Calculating Cocijo
Read 196 control systems and 795 targets.
Total connected: 195
Disconnected Controls
SystemDistance
Col 285 Sector AF-E b13-327.87528027


TargetDistanceControlsConfidenceAttackersInhabited?Advance
Canaharvas23.54899Col 285 Sector WY-F b12-3; Mapon; Col 285 Sector ZE-P c6-15; etcYes0.9
Col 285 Sector CA-E b13-126.32911HR 3048;No0.9
Asletae28.53633Col 285 Sector WY-F b12-0; Picenile; Col 285 Sector XT-F b12-7;Yes0.9
Col 285 Sector AF-E b13-029.28011Col 285 Sector AF-E b13-3; No0.9
Col 285 Sector AP-F b12-230.06711Col 285 Sector YT-F b12-0;No0.7
Col 285 Sector AF-P c6-1630.96533Col 285 Sector YY-F b12-0; Col 285 Sector AF-P c6-17; Col 285 Sector YY-F b12-3;No-0.6
Col 285 Sector BA-P c6-830.99211Col 285 Sector DA-E b13-8;No0.4
Col 285 Sector UD-G b12-531.26022Col 285 Sector ZE-P c6-6; Col 285 Sector ZE-P c6-11;No0.6
Col 285 Sector RS-H b11-331.39933Col 285 Sector SS-H b11-3; Vocovii; Col 285 Sector RS-H b11-4;No0.5
Col 285 Sector YY-F b12-531.44422Col 285 Sector AF-P c6-17; Col 285 Sector YY-F b12-3;No-0.5
Col 285 Sector YY-F b12-431.52944Col 285 Sector AU-F b12-2; Col 285 Sector AU-F b12-4; Col 285 Sector YY-F b12-3; etcNo-0.5
Col 285 Sector YT-Q c5-1131.56355Col 285 Sector YT-Q c5-12; Col 285 Sector YT-Q c5-14; Col 285 Sector YT-Q c5-10; etcNo-0.9
Col 285 Sector YT-Q c5-2331.58444Col 285 Sector VN-H b11-2; Col 285 Sector WN-H b11-5; Col 285 Sector YT-Q c5-25; etcNo-0.9
Col 285 Sector YY-F b12-131.58622Col 285 Sector AU-F b12-4; Col 285 Sector YY-F b12-3;No-0.4
Col 285 Sector UN-H b11-031.61411HIP 35633;No0.3
54 additional targets not listed, 69 total
Most of the perimeter is uninhabited, so skipping some of it isn't all that likely - though if recaptures move it onto reserves, AF-P c6-16 is a possible skipover.

-------------------------------------------

Calculating Thor
Read 126 control systems and 872 targets.
Total connected: 110
Disconnected Controls
SystemDistance
Rajuarpai11.4695589
Chanyaya16.10879151
HIP 1989416.20887223
Col 285 Sector IG-O c6-1417.71585625
HIP 2002419.46077284
Col 285 Sector SM-C b13-021.77609336
Col 285 Sector UH-C b13-121.81126877
Col 285 Sector UH-C b13-022.79575584
Col 285 Sector SM-C b13-123.95464872
HIP 1885724.61621433
Col 285 Sector JG-O c6-524.84190245
Col 285 Sector SM-C b13-225.94627111
Col 285 Sector SM-C b13-326.05759096
Col 285 Sector HL-O c6-430.23485545
Col 285 Sector HL-O c6-531.49809332
Col 285 Sector HL-O c6-331.52685177


TargetDistanceControlsConfidenceAttackersInhabited?Advance
Col 285 Sector FU-H b10-043.36122HIP 20807; Col 285 Sector OC-V d2-75;No-0.2
Col 285 Sector DZ-H b10-146.44622Col 285 Sector FU-H b10-2; Col 285 Sector FU-H b10-4;No0.2
Hyades Sector KB-O b6-248.15511Col 285 Sector FU-H b10-4;No0.2
No further targets possible
Thor starts the week with only four usable perimeter Controls, all in or near the outer FU-H b10 subsector. A complete Alert lockdown is very possible.

-------------------------------------------

Calculating Raijin
Read 168 control systems and 825 targets.
Total connected: 168

TargetDistanceControlsConfidenceAttackersInhabited?Advance
Nu Guang19.33011Snoqui;Yes0.9
Bormuninus24.35644Pegasi Sector MN-S b4-2; Pegasi Sector MN-S b4-0; Pegasi Sector UF-L a9-0; etcYes-0.3
Pegasi Sector GW-V b2-325.91822Pegasi Sector KC-U b3-6 (9.914 LY); Pegasi Sector BQ-Y d71;No-0.6
Jawul26.67522Chinas; Pegasi Sector KH-V c2-13;Yes0.2
Ngolite26.89488Pegasi Sector JH-U b3-8; Pegasi Sector RE-N a8-0; HIP 112595; etcYes0.8
Pegasi Sector QE-N a8-326.9741010Chakma; Pegasi Sector QE-N a8-0; Pegasi Sector UK-L a9-1; etcNo0.2
Pegasi Sector WK-L a9-327.26644Pegasi Sector NN-S b4-4; Pegasi Sector RE-N a8-0; Pegasi Sector RE-N a8-4; etcNo0.9
Pegasi Sector BQ-Y d10127.26911Pegasi Sector HH-U b3-4;No-0.8
Pegasi Sector VK-L a9-127.39277Pegasi Sector VK-L a9-0; Pegasi Sector UK-L a9-3; Pegasi Sector ZQ-J a10-1; etcNo0.7
Pegasi Sector PE-N a8-127.4191111Pegasi Sector DG-X c1-4; Pegasi Sector PE-N a8-3; Pegasi Sector PE-N a8-2; etcNo-0.3
Pegasi Sector ON-S b4-227.46211HIP 113076;No1
Pegasi Sector JS-Q a6-227.53177Pegasi Sector NY-O a7-1; Pegasi Sector EB-W b2-2; Pegasi Sector NY-O a7-5; etcNo0.4
Pegasi Sector KC-U b3-127.54766Pegasi Sector KC-U b3-2; Pegasi Sector BQ-Y d93; Pegasi Sector BQ-Y d71; etcNo-0.8
Pegasi Sector KH-V c2-2527.61622Pegasi Sector OI-S b4-4 (9.980 LY); Pegasi Sector KH-V c2-13;No0.1
Pegasi Sector OY-O a7-027.67055Pegasi Sector JH-U b3-9; Pegasi Sector NY-O a7-5; Pegasi Sector NY-O a7-2; etcNo0.6
84 additional targets not listed, 99 total
It wouldn't be too surprising for GW-V b2-3 to be skipped in favour of a forward-facing inhabited system.

-------------------------------------------

Calculating Hadad
Read 83 control systems and 912 targets.
Total connected: 82
Disconnected Controls
SystemDistance
Col 285 Sector TH-B b14-426.61885566


TargetDistanceControlsConfidenceAttackersInhabited?Advance
Col 285 Sector TS-Z b14-322.02411HR 2204 (9.988 LY);No0.9
Yan Zangata22.38511Col 285 Sector JW-M c7-10;Yes1
Col 285 Sector PM-B b14-526.05511Vasupari (9.991 LY);No0.8
Col 285 Sector XN-Z b14-127.10011Col 285 Sector KW-M c7-16;No-0.8
Col 285 Sector TH-B b14-329.67522Col 285 Sector RM-B b14-4; Col 285 Sector TH-B b14-4; No-0.9
Col 285 Sector KW-M c7-1029.77911Col 285 Sector VS-Z b14-6;No-0.6
Col 285 Sector PR-B b14-130.81111Col 285 Sector RM-B b14-6 (9.990 LY);No-0.3
No further targets possible
Hadad not quite as bad as Thor or Oya yet, but not doing well either.



Code:
-- Recaptures above (2 if confirmed, probability otherwise; exhausts below at exactly 1)
-- Taranis
Trianguli Sector BA-A d85:1
HIP 25670:1
Hyades Sector BV-O b6-4:1
Hyades Sector GW-W d1-87:1
Hyades Sector GW-W d1-81:1
-- Leigong
Arietis Sector AQ-P b5-2:1
Arietis Sector KM-W d1-93:1
Arietis Sector EW-N b6-1:1
HIP 6380:1
HIP 5685:1
-- Indra
64 Tauri:1
Arietis Sector LM-V b2-3:1
71 Tauri:1
HIP 20916:1
HIP 20577:1
-- Oya
Sambaho:1
Daruwach:1
Cephei Sector DQ-Y b1:1
HIP 8525:1
-- Cocijo
Col 285 Sector YT-F b12-2:1
Col 285 Sector SS-H b11-0:1
Col 285 Sector YT-F b12-1:1
Col 285 Sector YT-F b12-6:1
Col 285 Sector YT-F b12-4:1
-- Thor
HIP 19198:1
-- Raijin
Pegasi Sector IH-U b3-0:1
Pegasi Sector NN-S b4-10:1
Pegasi Sector LC-U b3-2:1
HIP 113535:1
Pegasi Sector OI-S b4-6:1
-- Hadad
Montioch:1
Col 285 Sector RH-B b14-2:1
Omumba:1
Col 285 Sector US-Z b14-1:1
 
Just hypothetically, if one were to start collapsing the targeting at M. Taranis, would it be the case that puncturing Trianguli Sector KR-W b1-1 would make Matshiru attack Nihal and leave only Hyades Sector IM-L b8-5 and Trianguli Sector JW-W b1-6 able to attack HIP 26688?

I am looking at a few options for the remainder of the week after a little more trimming at M. Leigong, and I think that doing the above would make it actually possible to adjust M. Taranis so that its only inhabited attacks are Nihal, Awara and Paeni. That would be a quite heavy sprint though; if visited, it is more likely that we could just deny it Senocidi and a couple of the more easily-guarded systems. Visiting it at all also competes a bit with deflating M. Cocijo a bit, or keeping the possible harvest opportunities open for helping where other Commanders have made partial progress!
 
Just hypothetically, if one were to start collapsing the targeting at M. Taranis, would it be the case that puncturing Trianguli Sector KR-W b1-1 would make Matshiru attack Nihal and leave only Hyades Sector IM-L b8-5 and Trianguli Sector JW-W b1-6 able to attack HIP 26688?
That looks right, I think.
I am looking at a few options for the remainder of the week after a little more trimming at M. Leigong, and I think that doing the above would make it actually possible to adjust M. Taranis so that its only inhabited attacks are Nihal, Awara and Paeni. That would be a quite heavy sprint though; if visited, it is more likely that we could just deny it Senocidi and a couple of the more easily-guarded systems. Visiting it at all also competes a bit with deflating M. Cocijo a bit, or keeping the possible harvest opportunities open for helping where other Commanders have made partial progress!
Definitely a tough challenge, given how long Taranis has been given a big fight on inhabited targets and free reign on uninhabited ones, the two shells are quite substantially different in distance now.
 
Definitely a tough challenge, given how long Taranis has been given a big fight on inhabited targets and free reign on uninhabited ones, the two shells are quite substantially different in distance now.

It was just about within capability, but either way it sounds as if it would be better now to tour those four Maelstroms which are not yet facing a designed catastrophe and give them just a few gaps in their unpopulated volume, so that those will start taking the place of better targets four weeks later when the real manipulation can begin.

Causing also a few reductions to attack strength is quite nice; something not captured in the reports, at risk of flooding them a bit of course, is how the recently-evicted Hyades Sector PN-T c3-9 was a 26.38 Ly unpopulated system back-attacking the 19.56 Ly inhabited 63 Eridani. Unlike most of those others, that was a particularly-if-not-uniquely gross attacker if allowed to stand, with over an order of magnitude strength difference!
 
Prediction updates (preliminary, as I expect there's still a few recaptures left). Testing a new feature for the tables - backwards attack potentials are underlined on the system list.

Taranis
TargetDistanceControlsConfidenceAttackersInhabited?Advance
Nihal21.44144Trianguli Sector KR-W b1-1; Matshiru; Hyades Sector KH-L b8-0; etcYes0.4
HIP 2668821.93633Matshiru; Hyades Sector IM-L b8-5; Trianguli Sector JW-W b1-6; Yes0.4
Awara21.99733Hyades Sector EB-N b7-0; HIP 23593; Hyades Sector GW-W d1-86; Yes0.4
HIP 2199125.78611Trianguli Sector JR-W b1-5 (9.904 LY); Yes0.4
Paeni26.7283329 e Orionis; Trianguli Sector ZJ-A b1; Hyades Sector YZ-O b6-0; Yes0.3
Ge27.68344Hyades Sector NS-T c3-14; Haushu; Hyades Sector ZZ-O b6-1; etcYes0.2
HIP 2692628.17033Haushu; Hyades Sector ZZ-O b6-1; Hyades Sector ZZ-O b6-2; Yes0.3
Trianguli Sector JW-W b1-128.92222Hyades Sector IM-L b8-5; Trianguli Sector JW-W b1-6; No0.6
Hyades Sector YZ-O b6-328.96922Trianguli Sector ZJ-A b1; Hyades Sector YZ-O b6-0; Yes0.2
Hyades Sector EG-N b7-529.05822Hyades Sector EG-N b7-3; Hyades Sector EG-N b7-4; No0.3
Hyades Sector EQ-O b6-429.07233Hyades Sector EQ-O b6-2; Hyades Sector DQ-O b6-2; Hyades Sector DQ-O b6-4; No-0.9
Hyades Sector XO-Q b5-429.26422Hyades Sector GW-W d1-82; Hyades Sector XO-Q b5-3; No-0.5
Hyades Sector VT-Q b5-229.26811Hyades Sector XO-Q b5-3; No-0.4
Nareg29.54111HIP 25840; Yes0.8
Hyades Sector EG-N b7-629.81822Hyades Sector EG-N b7-2 (10.015 LY); Vogulmangoi; No0.2
Still five inhabited systems at the top, but quite a few changes as to which five

Leigong
TargetDistanceControlsConfidenceAttackersInhabited?Advance
Pathamon22.06466HIP 7277; Arietis Sector JM-W d1-56; Arietis Sector MX-U c2-17; etcYes0.5
And that's the lot

Indra
There has been a recapture, but no changes as Indra is very tightly connected

Oya
TargetDistanceControlsConfidenceAttackersInhabited?Advance
Cephei Sector DQ-Y b222.14911HIP 7338 (9.988 LY); No0.5
Again, just the one target left

Cocijo
Recapture does not affect prediction

Thor
All Alert targets at Thor eliminated!

Raijin
Quite a few recaptures but they're on the outside so don't affect its short-term plans

Hadad
TargetDistanceControlsConfidenceAttackersInhabited?Advance
Col 285 Sector TS-Z b14-322.02411HR 2204 (9.988 LY); No0.9
Col 285 Sector PM-B b14-526.05511Vasupari (9.991 LY); No0.8
Down to just two targets
 
Accuracy result:
- Taranis: 100%
- Leigong: 100%
- Indra: 100%
- Oya: 0% (0 of 1). HIP 7338 attacked the inhabited HIP 2422 rather than the uninhabited Cephei Sector DQ-Y b2 (it could also have gone for the closer-to-the-Maelstrom inhabited Muncheim, but didn't)
- Cocijo: some late recaptures after the last update. These moved targeting as expected, 100% when using the final recapture list.
- Thor: NaN% (correctly predicted)
- Raijin: 100%
- Hadad: 100%

So just one miss this week, as Oya picks a more distant inhabited target for its one usable Control.

I'll see if I can update the prediction tables to show this sort of alternate targeting a bit better.
 
I was just checking for possible attackers set wrongly but I think HIP 7338 could be right as the attacker.
The cycle 28 attack sort of isolate it so any problems can't be that far back.
In cycle 29 if Cephei Sector DQ-Y b1 was somehow unavailable then HIP 8525 hits Poqomathi and HIP 7338 hits Gliese 3050 to put it on time-out, but I don't think there was anything else which could have hit HIP 2422 now.

It's probably your idea of inhabited being considered closer or higher priority.
Then again, not attacking Muncheim seems too weird - are we sure there wasn't some way that HIP 8525 could have been the attacker?
Both Muncheim and HIP 2422 fit the priority change which skipped Cephei Sector DQ-Y b2, and HIP 8525 can see HIP 2422 but not Muncheim...
 
If last time HIP 8525 rather than HIP 7338 hit Gliese 3050, that would work - but then we'd instead need a reason that happened given that "use the closest control to the maelstrom" has worked so consistently otherwise for months.

That could also have happened of course if HIP 7338 had hit a target the week before ... the catch there is that I had both 7338 and 8525 marked as offline that week, because they'd have been the obvious places to launch the attacks on DQ-Y b2 and Muncheim which did happen.

A rule like "if the selected control for an uninhabited target can see inhabited targets, attack the furthest of those instead" is possible.
 
Narwhal Nose report generated 29 June

-------------------------------------------

Systems are listed in order of priority, and in general the first five would be expected to be hit by Alerts, with a variable number of reserve targets shown depending on confidence levels. Predictions made early in the week may be reissued later if Control recaptures materially affect them.

Table key
Name
: Name of system considered at threat of Alert.
Distance: The distance in LY to the Maelstrom. A primary component of Thargoid prioritisation.
Controls: The number of Controls which can theoretically attack this system this week.
Confidence: The confidence that any Control can attack this system this week. Numbers under 1 should be treated as increasingly unlikely, while numbers above 2 are almost certain within the constraints of the model.
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.
Inhabited: Whether the system contains standing human population.
Advance: The approximate direction of the Alert relative to the Maelstrom. +1=towards Sol, -1=away from Sol, 0=perpendicular to Sol

-------------------------------------------

Calculating Taranis
Read 112 control systems and 883 targets.
Total connected: 107
Disconnected Controls
SystemDistance
HIP 2567015.28147367
Trianguli Sector KR-W b1-118.60194147
Matshiru19.81269716
Hyades Sector IM-L b8-525.77177856
Trianguli Sector JW-W b1-626.91604787


TargetDistanceControlsConfidenceAttackersInhabited?Advance
Senocidi20.26411Hyades Sector GW-W d1-87;Yes-0.4
Trianguli Sector GG-Y c1826.11311Trianguli Sector CA-A c14;Yes1
Namayu27.09522Trianguli Sector EQ-Y b5; Trianguli Sector EQ-Y b4;Yes0.5
Ge27.68355Hyades Sector GW-W d1-81; Hyades Sector NS-T c3-14; Haushu; etcYes0.2
HIP 2692628.17044Hyades Sector NS-T c3-14; Haushu; Hyades Sector ZZ-O b6-1; etcYes0.3
Pentam28.87355Haushu; Hyades Sector NS-T c3-12; Hyades Sector ZZ-O b6-1; etcYes0.3
Trianguli Sector JW-W b1-128.92222Hyades Sector IM-L b8-5; Trianguli Sector JW-W b1-6; No0.6
Hyades Sector YZ-O b6-328.96922Trianguli Sector ZJ-A b1; Hyades Sector YZ-O b6-0; Yes0.2
Hyades Sector EG-N b7-529.05822Hyades Sector EG-N b7-3; Hyades Sector EG-N b7-4;No0.3
Hyades Sector EQ-O b6-429.07233Hyades Sector EQ-O b6-2; Hyades Sector DQ-O b6-2; Hyades Sector DQ-O b6-4;No-0.9
Hyades Sector XO-Q b5-429.26422Hyades Sector GW-W d1-82; Hyades Sector XO-Q b5-3;No-0.5
Hyades Sector VT-Q b5-229.26811Hyades Sector XO-Q b5-3;No-0.4
Nareg29.54111HIP 25840;Yes0.8
Hyades Sector EG-N b7-629.81822Hyades Sector EG-N b7-2 (10.015 LY); Vogulmangoi;No0.2
Hyades Sector ZZ-O b6-729.98422Hyades Sector ZZ-O b6-1; Hyades Sector ZZ-O b6-2;No0.2
26 additional targets not listed, 41 total
6 inhabited targets in the top 6 so this should be fairly reliable as a starter prediction.

-------------------------------------------

Calculating Leigong
Read 136 control systems and 863 targets.
Total connected: 132
Disconnected Controls
SystemDistance
Arietis Sector AQ-P b5-223.62518601
HR 45727.84494245
Arietis Sector VO-R b4-133.13603884
Arietis Sector VO-R b4-436.02875642


TargetDistanceControlsConfidenceAttackersInhabited?Advance
Arietis Sector AQ-P b5-317.21411Arietis Sector AQ-P b5-2; No0.4
Baudani24.96410.2Arietis Sector AQ-P b5-2; Yes0.5
Arietis Sector JM-W d1-5728.84311Arietis Sector EW-N b6-1;No0.9
Arietis Sector WO-R b4-435.68011Arietis Sector VO-R b4-4 (9.937 LY); No0.6
Arietis Sector DW-N b6-437.58711HIP 6380;No0.5
Hyades Sector LY-I b9-342.59911HIP 5685;No0.6
No further targets possible
Here's the first demo of the new formatting. AQ-P b5-2 could launch a backwards attack (underlined) on b5-3. But it's also the only one targeting the inhabited Baudani so it gets a secondary entry for that with much lower confidence and a strikethrough in the attacker list.

Even if not interfered with further, only one of the top two can happen, of course.


-------------------------------------------

Calculating Indra
Read 154 control systems and 838 targets.
Total connected: 154

TargetDistanceControlsConfidenceAttackersInhabited?Advance
HIP 2048521.436242463 Tauri; 64 Tauri; 71 Tauri; etcYes1
HR 140324.66499HR 1354 (9.991 LY); HIP 20712; Arietis Sector JR-V b2-4; etcYes0.9
65 Kappa Tauri25.42466HIP 20712; Arietis Sector JR-V b2-4; Arietis Sector JR-V b2-1; etcYes0.8
69 Upsilon Tauri26.47155Arietis Sector JR-V b2-4; Arietis Sector JR-V b2-1; HIP 21008; etcYes0.8
Arietis Sector DQ-Y c1826.58944Arietis Sector HG-X b1-3; Arietis Sector HG-X b1-4; Arietis Sector DQ-Y c9; etcYes-0.4
HIP 2138026.61055Arietis Sector JR-V b2-1 (9.994 LY); HIP 21008; Arietis Sector TY-P a6-0; etcYes0.8
HIP 2085026.986141477 Theta-1 Tauri; 70 Tauri; HIP 20815; etcYes0.9
HIP 2147427.124111186 Rho Tauri; 70 Tauri; HIP 20815; etcYes1
48 Tauri27.453141470 Tauri; HIP 20815; HR 1358; etcYes1
Hyades Sector LC-U b3-327.51244Hyades Sector NN-S b4-0 (9.980 LY); Hyades Sector LC-U b3-4; Hyades Sector FB-X c1-17; etcNo-1
HIP 2131727.5151111HIP 20815; 92 Sigma-2 Tauri; HIP 20741; etcNo1
Hyades Sector VK-L a9-027.65066Hyades Sector NN-S b4-4; Hyades Sector AR-J a10-0; HIP 21788; etcNo-0.3
HIP 2082627.6826679 b Tauri; HR 1358; HIP 20616; etcYes0.9
HIP 2071927.7171413.2HIP 20577 (9.953 LY); Hyadum II; HIP 20815; etcYes1
83 additional targets not listed, 97 total
Indra continues with a lot of strongly-connected inhabited systems at the top of the list. Likely to all go through.

-------------------------------------------

Calculating Oya
Read 33 control systems and 962 targets.
Total connected: 26
Disconnected Controls
SystemDistance
Chernobo15.57607967
Cephei Sector BV-Y b215.98888774
Tougeir16.22455941
Liu Huang17.75687587
Akbakara18.17006789
HIP 2432918.93453463
Muchihiks19.56140173


TargetDistanceControlsConfidenceAttackersInhabited?Advance
Cephei Sector ZZ-Y b314.94111Chernobo; No-0.2
HIP 404118.52822Ardhri (9.927 LY); Sambaho;No0.3
HIP 300618.93022Sambaho; Daruwach;No0.2
Lahua19.36322Tougeir; Muchihiks; Yes0.9
Cephei Sector ZE-A c819.89622HIP 10778; Daruwach;No-0.4
Gliese 903520.49421.2HIP 10778; Daruwach;Yes-0.5
Cephei Sector DQ-Y b222.14911HIP 8525;No0.5
No further targets possible
HIP 10778 could choose to jump forward to Gliese 9035, though if anything above that is blocked, Daruwach just skips back to ZE-A to complete the five.
I've assumed previous calculations were good and HIP 8525 is the active one of the 8525/7338 pair - if it's actually 8525 used this week so 7338 is ready for next week, then Muncheim is a possible fallback for DQ-Y b2.


-------------------------------------------

Calculating Cocijo
Read 190 control systems and 803 targets.
Total connected: 190

TargetDistanceControlsConfidenceAttackersInhabited?Advance
Khwal21.53077Mapon; Col 285 Sector ZE-P c6-15; Col 285 Sector ZE-P c6-16; etcYes1
Hez Ur22.00111Col 285 Sector WY-F b12-5;Yes0.7
Desurinbin25.1051010Col 285 Sector SS-H b11-5; Col 285 Sector SS-H b11-4; Col 285 Sector SS-H b11-0; etcYes0.2
Col 285 Sector UD-G b12-225.94733Kurumanit; Col 285 Sector WY-F b12-1; 19 Puppis; Yes0.4
Col 285 Sector CA-E b13-126.32922Col 285 Sector YT-F b12-6; Col 285 Sector YT-F b12-1;No0.9
Col 285 Sector AF-E b13-526.49110.2Col 285 Sector YT-F b12-6; Yes0.9
Col 285 Sector UD-G b12-531.26022Col 285 Sector ZE-P c6-6; Col 285 Sector ZE-P c6-11;No0.6
Col 285 Sector RS-H b11-331.39944Col 285 Sector SS-H b11-0; Col 285 Sector SS-H b11-3; Vocovii; etcNo0.5
Col 285 Sector YY-F b12-531.44422Col 285 Sector AF-P c6-17; Col 285 Sector YY-F b12-3;No-0.5
Col 285 Sector YY-F b12-431.52944Col 285 Sector AU-F b12-2; Col 285 Sector AU-F b12-4; Col 285 Sector YY-F b12-3; etcNo-0.5
Col 285 Sector YT-Q c5-1131.56322Col 285 Sector US-H b11-1; Col 285 Sector WN-H b11-4;No-0.9
Col 285 Sector YT-Q c5-2331.58444Col 285 Sector VN-H b11-2; Col 285 Sector WN-H b11-5; Col 285 Sector YT-Q c5-25; etcNo-0.9
Col 285 Sector YY-F b12-131.58622Col 285 Sector AU-F b12-4; Col 285 Sector YY-F b12-3;No-0.4
Col 285 Sector UN-H b11-031.61411HIP 35633;No0.3
Col 285 Sector CA-E b13-231.71111Col 285 Sector YT-F b12-1;No0.9
Col 285 Sector YT-Q c5-2231.75644Col 285 Sector WN-H b11-5; Col 285 Sector YT-Q c5-25; Col 285 Sector WN-H b11-4; etcNo-0.9
52 additional targets not listed, 68 total
Chance for YT-F b12-6 to skip ahead and attack a fifth inhabited system.

-------------------------------------------

Calculating Thor
Read 117 control systems and 881 targets.
Total connected: 98
Disconnected Controls
SystemDistance
Rajuarpai11.4695589
Chanyaya16.10879151
HIP 1989416.20887223
Col 285 Sector IG-O c6-1417.71585625
HIP 2002419.46077284
Col 285 Sector SM-C b13-021.77609336
Col 285 Sector UH-C b13-121.81126877
Col 285 Sector UH-C b13-022.79575584
Col 285 Sector SM-C b13-123.95464872
HIP 1885724.61621433
Col 285 Sector JG-O c6-524.84190245
Col 285 Sector SM-C b13-225.94627111
Col 285 Sector SM-C b13-326.05759096
Col 285 Sector HL-O c6-430.23485545
Col 285 Sector HL-O c6-531.49809332
Col 285 Sector HL-O c6-331.52685177
Col 285 Sector HF-G b11-232.45495677
Col 285 Sector IA-G b11-235.8304111
Col 285 Sector GF-G b11-536.82861224
Thor's connectivity is an increasing mess.

TargetDistanceControlsConfidenceAttackersInhabited?Advance
Col 285 Sector NG-E b12-422.21733Col 285 Sector NG-E b12-5; Col 285 Sector NG-E b12-2; Col 285 Sector NG-E b12-1; No0.6
Col 285 Sector NG-E b12-324.09411Col 285 Sector NG-E b12-2;No0.5
Col 285 Sector JA-G b11-326.12233Col 285 Sector OC-V d2-96; Col 285 Sector EA-Q c5-8; Col 285 Sector HF-G b11-2; No0.5
Col 285 Sector LL-E b12-127.47111Col 285 Sector NG-E b12-1;No0.6
Col 285 Sector LL-E b12-027.80111HIP 20509; No0.8
Col 285 Sector JG-O c6-1428.18533Col 285 Sector SM-C b13-0; Col 285 Sector JG-O c6-5; Col 285 Sector SM-C b13-3; No0.5
Col 285 Sector JG-O c6-1331.07211Col 285 Sector JG-O c6-5; No0.5
Almar31.78411Col 285 Sector SM-C b13-3; Yes0.3
Col 285 Sector SI-T d3-8932.77211Col 285 Sector HL-O c6-5; No0.3
Hyades Sector MM-M b7-135.76944HIP 20489; Col 285 Sector HF-G b11-2; Col 285 Sector IA-G b11-2; etcNo0.6
No further targets possible
A lot of the systems cleared in previous counter-attacks on Thor have now come round for targeting again as it attempts to regain the lost ground. Unlikely in the default case to get as far as Almar.

-------------------------------------------

Calculating Raijin
Read 160 control systems and 831 targets.
Total connected: 160

TargetDistanceControlsConfidenceAttackersInhabited?Advance
Pegasi Sector QZ-M a8-026.94011Pegasi Sector HH-U b3-4;No-0.8
Pegasi Sector QE-N a8-326.9741010Chakma; Pegasi Sector QE-N a8-0; Pegasi Sector UK-L a9-1; etcNo0.2
Pegasi Sector WK-L a9-127.01333Pegasi Sector NN-S b4-4; Pegasi Sector RE-N a8-0; Pegasi Sector RE-N a8-4;No0.9
Pegasi Sector LY-O a7-027.18666Pegasi Sector DG-X c1-5; Pegasi Sector DG-X c1-4; Gl 886.1 B; etcNo-0.4
Pegasi Sector WK-L a9-327.26622Pegasi Sector RE-N a8-0; Pegasi Sector RE-N a8-4;No0.9
Pegasi Sector VK-L a9-327.32955Pegasi Sector VK-L a9-0; HIP 113535; HIP 112595; etcNo0.8
Pegasi Sector VK-L a9-127.39266Pegasi Sector UK-L a9-3; Pegasi Sector ZQ-J a10-1; Ixbaksha; etcNo0.7
Pegasi Sector PE-N a8-127.4191111Pegasi Sector DG-X c1-4; Pegasi Sector PE-N a8-3; Pegasi Sector PE-N a8-2; etcNo-0.3
Pegasi Sector ON-S b4-227.46211HIP 113076;No1
Pegasi Sector JS-Q a6-227.53177Pegasi Sector NY-O a7-1; Pegasi Sector EB-W b2-2; Pegasi Sector NY-O a7-5; etcNo0.4
Pegasi Sector KC-U b3-127.54766Pegasi Sector KC-U b3-2; Pegasi Sector BQ-Y d93; Pegasi Sector BQ-Y d71; etcNo-0.8
Pegasi Sector KH-V c2-2527.61622Pegasi Sector OI-S b4-4 (9.980 LY); Pegasi Sector KH-V c2-13;No0.1
Pegasi Sector OY-O a7-027.67055Pegasi Sector JH-U b3-9; Pegasi Sector NY-O a7-5; Pegasi Sector NY-O a7-2; etcNo0.6
Pegasi Sector SP-L a9-127.8171010Pegasi Sector UK-L a9-5; Pegasi Sector UK-L a9-1; Pegasi Sector UK-L a9-2; etcNo0.3
82 additional targets not listed, 96 total
An unusually uninhabited week at Raijin, but no obvious reason to expect anything other than the top 5 yet.

-------------------------------------------

Calculating Hadad
Read 77 control systems and 919 targets.
Total connected: 76
Disconnected Controls
SystemDistance
Col 285 Sector VS-Z b14-324.11759116


TargetDistanceControlsConfidenceAttackersInhabited?Advance
Bi Dhorora18.46633Col 285 Sector VN-Z b14-0; Montioch; Omumba;Yes0.3
Vogulu20.72833Montioch; Col 285 Sector RH-B b14-5; Col 285 Sector RH-B b14-4;Yes0.7
Col 285 Sector SX-Z b14-123.45333Col 285 Sector US-Z b14-1 (9.970 LY); Col 285 Sector SX-Z b14-0; Col 285 Sector OR-B b14-4;No0.4
Col 285 Sector RM-B b14-123.59333Col 285 Sector RM-B b14-2; Col 285 Sector RM-B b14-8; Col 285 Sector RM-B b14-0;No-0.9
Col 285 Sector OR-B b14-825.27333Col 285 Sector KW-M c7-12; Col 285 Sector OR-B b14-4; Col 285 Sector OR-B b14-9; No-0
Col 285 Sector OR-B b14-626.01822Col 285 Sector OR-B b14-4; Col 285 Sector OR-B b14-9;No-0.1
Col 285 Sector KW-M c7-2426.68222Col 285 Sector VS-Z b14-0; Col 285 Sector WN-Z b14-5;No-0.7
Col 285 Sector OR-B b14-026.73022Col 285 Sector KW-M c7-31; Col 285 Sector PM-B b14-3;No0.2
HIP 3271827.17711Col 285 Sector KW-M c7-29;No-0.3
Col 285 Sector OR-B b14-727.90711Col 285 Sector OR-B b14-9;No-0.2
Col 285 Sector RN-T d3-7929.74022Col 285 Sector RM-B b14-8 (9.951 LY); Col 285 Sector RM-B b14-0;No-0.9
Col 285 Sector RN-T d3-8030.57311Col 285 Sector RM-B b14-0;No-0.9
No further targets possible
As with Thor, a lot of systems cleared 4 weeks ago are now back on the target list.



Code:
-- exhausts below, recaptures above
-- Taranis
Trianguli Sector KR-W b1-1:1
Matshiru:1
Hyades Sector EB-N b7-0:1
Trianguli Sector JR-W b1-5:1
Trianguli Sector KR-W b1-1:1
-- Leigong
HIP 7277:1
-- Indra
Arietis Sector IG-X b1-4:1
Hyadum I:1
HIP 19934:1
HIP 20419:1
HIP 20480:1
-- Oya
HIP 7338:1
-- Cocijo
Col 285 Sector WY-F b12-3:1
Col 285 Sector WY-F b12-0:1
Col 285 Sector YT-F b12-0:1
Col 285 Sector YY-F b12-0:1
Col 285 Sector DA-E b13-8:1
-- Thor
-- Raijin
Snoqui:1
Pegasi Sector MN-S b4-2:1
Pegasi Sector KC-U b3-6:1
Chinas:1
Pegasi Sector JH-U b3-8:1
-- Hadad
HR 2204:1
Vasupari:1
 
A rule like "if the selected control for an uninhabited target can see inhabited targets, attack the furthest of those instead" is possible.
Taking a look at earlier - that rule fits the cycle 30 attack just now but doesn't explain targets skipped before.
Possible rules from before (inhabited lowers distance etc) also don't explain why some targets weren't skipped now!

So the cycle 27 Oya attacks skipped some unpopulated targets to hit Orong and Benanekpeno, but the attackers skipped can't have retargeted because they are 20-40 LY away from the attacks.
Even more strange is how they skipped HIP 38225 (inhabited+starport) to do it, similar to cycle 28 Indra skipping Arietis Sector DQ-Y c18 (inhabited planetary only).
Those Indra attackers also can't see HIP 21380 which was chosen instead - most or all previous cases were totally different attackers rather than one rogue attacker breaking the thargoid SOP.
Not to say HIP 7338 can't be the first to think like that, but it's either that or some other rule where their new plan coincidentally also used HIP 7338 to attack, or maybe they run it through GPT for suggestions.

If we're skipping stuff, the earlier ideas don't explain why Indra failed to skip Arietis Sector JR-V b2-2 just now.
A lot of simple rule ideas (eg. inhabited lowers distance) also fail to explain why Cocijo didn't reach all the way down to attack Na Zha (last on our list).

Also I'm guessing we're leaving Arietis Sector AQ-P b5-2 around to see if it hits Baudani :D
 
Taking a look at earlier - that rule fits the cycle 30 attack just now but doesn't explain targets skipped before.
No, I've come to much the same conclusion - accounting for any combination of distance, habitation and direction towards Sol, I can't make a rule that picks all the further out targets they did without also picking targets they didn't. This is the first time the skipped system has been by the same Control, too, which does suggest it's about changes to the target sort rather than the behaviour of the Controls themselves.

So I'd guess there's some other parameter that's important, but I can't think what yet.

So far we've only seen this at Oya and Indra, but those are extremely different environments ... so why not anywhere else?

Also I'm guessing we're leaving Arietis Sector AQ-P b5-2 around to see if it hits Baudani :D
Similarly Col 285 Sector YT-F b12-6 at Cocijo, if you want to leave test options open.
 
Finagling in some offline test rules myself for skipping an unpop + further inhabs shows up some interesting attack options earlier :D
Cycle 30 Oya before-
skip1.png


Cycle 30 Oya with skipping an unpop-
skip2.png

When HIP 7338 can skip and hit Muncheim, pushing FBX into 2nd also brought HIP 2422 into play, but cancelled because FBX was already purged, so it needs to know it can skip some more.
Also looks like BD+77 84 totally could have hit 47 Cassiopeiae

Cycle 30 Oya hitting multiple after skipping an unpop-
skip3.png

Pushed FBX into 2nd AGAIN at HIP 2422, so in a sense Gliese 9843 could've been in play as well, but it sort of misses the fact that it can't push FBX into 2nd in 2 places so hitting HIP 2422 would put FBX 1st at Muncheim again.
Need to think of a clear way to show that cascade while also not showing 3 targets.

Cycle 31 (that's now) Leigong check with those rules-
skip4.png

Got Baudani, but also got YUP though - not actually sure if we've had that happen "normally" (ie. not chaos at Thor).
Unless it's happened, I can't see it missing an unpop to hit a weaker unpop.

Cycle 31 Leigong with only the first unpop target-
skip5.png

That case matches now but I'll check through all retro effects of that later in case that rule would have messed anything up.
It's probably fine if all it does is add possibilities and we'll see if it flags up a load of questions about why they didn't attack better systems.
 
Unless it's happened, I can't see it missing an unpop to hit a weaker unpop.
Once at Indra, w/c 8 June. Skips Hyades Sector LC-U b3-3 (unpopulated, 27.512) to hit HIP 21317 (unpopulated, 27.515)

That's one of the cases that meant I considered direction as a possible parameter - LC-U is almost directly backwards, HIP is almost directly forwards.
 
Back
Top Bottom