Analysing the Thargoid Simulation

Ideas so far (not ruled out yet):
  • Recapturing eight [1] (as opposed to seven last week) control systems at a Maelstrom in a single week gives a bonus reduction in Alert capacity
  • Recapturing ten or eleven (as opposed to nine last week) control systems globally in a single week gives a bonus reduction in Alert capacity
  • Just one of those things
Ideas so far (unlikely)
  • Leigong-style invisible Alert. The total Alert count on the summary matches at 39 the number visible on the map, unlike in the Leigong situation
  • The Thargoid process sets a list+reserves at the start of the week, of finite length. I don't think this one works - last week cleared out as many potential systems from the original list without stopping them, and it would be an unusual mechanism compared with the other simulations.
  • The undocumented extra weeks of recovery confused it. But they seem to have been fine with that elsewhere and in other weeks.
  • The gap between Bi Dhorora and MR-M is too large and it doesn't want to get too far out of spherical. Thor's gap is even larger with no issue, though.
  • No available control systems. Even if for some reason the ones on the prediction were all unavailable, L2 Puppis was next in line with 5 separate Controls targeting it. We should be long past the stage where even Thor can't find 5 targets a week.
[1] Lucky number?
 
Last edited:
Prediction quality:
  • Taranis: 100%
  • Leigong: 100%
  • Indra: 80% (HIP 20890 went to an extra Recovery week)
  • Oya: 100%
  • Cocijo: 100%
  • Thor: 60% (Unktety went to extra Recovery, while HL-O c6-15 from SI-T d3-89 was skipped)
  • Raijin: 100%
  • Hadad: 80%? 75%? (Muruidooges went to extra Recovery, 4 of top 5 predicted correctly, but number of alerts also mispredicted)
Doesn't look like there's a lot we can do at this stage to deal with systems having 4-week recoveries but being shown right up until the cycle as being 3-week scheduled in-game. Flagging them as dubious is going to have to be it for now; maybe U15 will happen to fix the bug.

HL-O c6-15 was a data entry error on my part rather than a model flaw: SI-T d3-89 had clearly been used the previous week but I didn't put it in the exceptions file properly.
 
Narwhal Nose report generated 27 April

No changes to the model this time other than to accept that we can't predict 4-week recoveries for now and add extra reserves to affected maelstroms.

30 of the 40 overall are predicted to be inhabited, which would be the highest ever - even allowing for extended recoveries and some redirections at Hadad there's a very high chance of equalling the 26 hit on 23 February.
-------------------------------------------

Calculating Taranis
Read 125 control systems and 870 targets.

TargetDistanceControlsConfidenceAttackersInhabited?Advance
Imeut19.1377*HIP 25670; Hyades Sector FB-N b7-3; HIP 25679; etcYes0.8
Ebisu21.0555Hyades Sector BV-O b6-4; Hyades Sector EB-N b7-0; Hyades Sector GW-W d1-86; etcYes0.1
HIP 2668821.9454.4HIP 25670; HIP 25679; Matshiru; etcYes0.4
Hyades Sector AV-O b6-523.9832.6Hyades Sector GW-W d1-87; Hyades Sector AV-O b6-4; Hyades Sector GW-W d1-76;Yes-0.1
Vukurbeh24.2521.5Trianguli Sector KR-W b1-1; Matshiru;Yes0.8
Paeni26.734429 e Orionis; Hyades Sector GW-W d1-81; Trianguli Sector ZJ-A b1; etcYes0.3
Trianguli Sector JW-W b1-626.9210.8Hyades Sector IM-L b8-5;No0.6
Lovaroju26.9333Hyades Sector PN-T c3-7; Hyades Sector QN-T c3-11; Hyades Sector PN-T c3-5;Yes-1
Namayu27.1022Trianguli Sector EQ-Y b5; Trianguli Sector EQ-Y b4;Yes0.5
All fairly high confidence this time, though a chance of getting to Paeni if Imeut goes to four weeks.

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

Calculating Leigong
Read 164 control systems and 831 targets.

TargetDistanceControlsConfidenceAttackersInhabited?Advance
Garongxians28.1544Jementi; Ceti Sector XJ-A c18; HIP 10616; etcYes0.8
Wolf 12128.9210.8Arietis Sector CQ-P b5-2;Yes0.5
Arietis Sector UO-R b4-430.9711Arietis Sector VO-R b4-3;No0.6
Arietis Sector CQ-P b5-332.0832.8HIP 10616; Arietis Sector YJ-R b4-4; Arietis Sector CQ-P b5-1;No0.8
Heng34.1121.1HIP 10616; Arietis Sector YJ-R b4-4;Yes0.8
Arietis Sector YJ-R b4-335.3720.8Arietis Sector YJ-R b4-4; Arietis Sector CQ-P b5-1;No0.6
Arietis Sector VO-R b4-436.0333Arietis Sector VO-R b4-2; Arietis Sector VO-R b4-1; Arietis Sector VO-R b4-0;No0.7
Ceti Sector ZU-Y b336.4533Ceti Sector ZU-Y b1; Ceti Sector ZU-Y b2; HIP 6679;No0.8
Dao Tzu36.6410.2Arietis Sector CQ-P b5-1;Yes0.8
Arietis Sector DW-N b6-437.5922Arietis Sector JM-W d1-83; HIP 6380;No0.5
Arietis Sector DW-N b6-338.3232Arietis Sector JM-W d1-83; HIP 6380; HIP 6869;No0.5
Arietis Sector ZU-P b5-038.3332.7Arietis Sector ZU-P b5-4; Arietis Sector VO-R b4-0; Arietis Sector ZU-P b5-2;No0.8
Some low-confidence estimates here: in theory if HIP 10616 hits Garongxians and then YJ-R b4-4 hits CQ-P b5-3, there'll be nothing left for Heng. In practice, they'll probably get all three.

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

Calculating Indra
Read 149 control systems and 845 targets.

TargetDistanceControlsConfidenceAttackersInhabited?Advance
HIP 2048521.44252563 Tauri; 64 Tauri; Hyadum I; etcYes1
HIP 1915721.6511*Arietis Sector IG-X b1-4;Yes-0.6
HIP 2089021.891615.6HIP 20577; HR 1354; HIP 20679; etcYes0.9
Kagutsuchi22.5022Arietis Sector LM-V b2-3; Arietis Sector NH-V b2-0;Yes-0.4
HIP 2089923.092422.571 Tauri; HIP 20916; HIP 20577; etcYes1
HIP 2049123.3465.9HIP 20480; HIP 20712; Arietis Sector JR-V b2-4; etcYes0.4
HIP 2049224.042220.271 Tauri; HIP 20916; HIP 20577; etcYes1
Arietis Sector JR-V b2-226.2976HIP 20480; HIP 20712; Arietis Sector JR-V b2-4; etcNo0.6
Another potential for a 4-week recovery to throw things off but otherwise this is pretty densely-packed space.

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

Calculating Oya
Read 80 control systems and 915 targets.

TargetDistanceControlsConfidenceAttackersInhabited?Advance
Lahua19.3633Tougeir; Muchihiks; Cephei Sector CV-Y b1;Yes0.9
HIP 691320.3644HR 1107; HIP 3006; Cephei Sector EB-X b1-1; etcYes-0
Gliese 903520.4944HIP 10778; Daruwach; Cephei Sector ZE-A c8; etcYes-0.5
Minawara23.4233Cephei Sector FB-X b1-1; Cephei Sector FB-X b1-0; Cephei Sector EB-X b1-4;Yes0.6
Poqomathi24.1444Cephei Sector DQ-Y b1; HIP 8525; Cephei Sector DQ-Y b2; etcYes0.6
Chelka25.0511Cephei Sector ZE-A d69;Yes-0.5
HIP 3822526.9621.8Lyncis Sector YF-O b6-1; Ikpen;Yes-0.3
Orong27.1332HR 1107; Ikpen; Cephei Sector YJ-A c8;Yes-0.2
Benanekpeno27.1921.1HR 1107; Cephei Sector YJ-A c8;Yes0
If true this would be exactly the same set of Alerts as three weeks ago, which is what the Oya defense strategy should expect to be directing the Thargoids to.

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

Calculating Cocijo
Read 197 control systems and 796 targets.

TargetDistanceControlsConfidenceAttackersInhabited?Advance
Col 285 Sector BA-P c6-1027.8522Col 285 Sector OS-T d3-106; Col 285 Sector BA-P c6-4;No0.4
Asletae28.5433Col 285 Sector WY-F b12-0; Picenile; Col 285 Sector XT-F b12-7;Yes0.9
Laumas29.2788*Col 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 AP-F b12-230.0733Col 285 Sector YT-F b12-2; Col 285 Sector YT-F b12-0; Col 285 Sector YT-F b12-5;No0.7
Col 285 Sector US-H b11-130.1233Col 285 Sector AF-P c6-1; Col 285 Sector YT-Q c5-12; Col 285 Sector YT-Q c5-10;No-1
HIP 3946830.3477Col 285 Sector AU-F b12-2; Col 285 Sector AU-F b12-3; Col 285 Sector OS-T d3-115; etcNo-0.1
Col 285 Sector YY-F b12-630.3533Col 285 Sector YY-F b12-0; Col 285 Sector AF-P c6-17; Col 285 Sector YY-F b12-3;No-0.5
Might miss Laumas but otherwise these all look pretty solid

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

Calculating Thor
Read 160 control systems and 834 targets.

TargetDistanceControlsConfidenceAttackersInhabited?Advance
Unktety25.3611HIP 19198;Yes1
HIP 2172429.6611Col 285 Sector SI-T d3-89;Yes0
Col 285 Sector HL-O c6-430.2311Col 285 Sector HL-O c6-5;No0.2
Col 285 Sector HL-O c6-1538.4544Almar; Col 285 Sector HL-O c6-14; Col 285 Sector QR-C b13-4; etcNo0.3
Col 285 Sector QR-C b13-338.9132.3Almar; Col 285 Sector HL-O c6-14; Col 285 Sector QR-C b13-4;No0.3
Mangwutja39.7122Auaker; Col 285 Sector GL-O c6-15;Yes0.8
Warimpe40.4021Auaker; Col 285 Sector GL-O c6-15;Yes0.8
HIP 1851340.4711Col 285 Sector LB-O c6-3;No-0.6
Col 285 Sector HL-O c6-1940.7510.8Col 285 Sector ML-E b12-0;No0.2
Col 285 Sector HF-G b11-541.2743.5HIP 21548; Col 285 Sector CF-Q c5-3; Col 285 Sector HF-G b11-4; etcNo0.5
HIP 2203141.3431.5HIP 21548; Col 285 Sector LL-E b12-5; Col 285 Sector CF-Q c5-3;No0.6
HIP 1827141.4611Col 285 Sector QX-U d2-48;No-0.5
Col 285 Sector FU-H b10-241.4811Col 285 Sector IA-G b11-2;No0.2
Col 285 Sector FU-H b10-341.5011HIP 20807;No0.1
Assuming I didn't mess up again with the inactive system list, there's a good chance of a 100% here despite the low paper confidence.

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

Calculating Raijin
Read 165 control systems and 829 targets.

TargetDistanceControlsConfidenceAttackersInhabited?Advance
HIP 11636020.9033*Pegasi Sector IH-U b3-0; Pegasi Sector BQ-Y d71; Pegasi Sector GW-V b2-3;Yes-0.5
Pegasi Sector NN-S b4-421.1455HIP 112823; Pegasi Sector NN-S b4-5; Pegasi Sector JH-U b3-8; etcNo0.9
Holvandalla21.481010Pegasi Sector NN-S b4-10; Kaurukat; Humarala; etcYes0.6
Pegasi Sector NN-S b4-323.8354.8HIP 112823; Pegasi Sector ZQ-J a10-0; Pegasi Sector ZQ-J a10-1; etcNo0.8
Isla23.9044Pegasi Sector LC-U b3-2; HIP 116542; Wanmi; etcYes-0.1
HIP 11717724.7611Pegasi Sector DG-X c1-6;Yes-0.1
Pegasi Sector EB-W b2-726.9355Pegasi Sector IH-U b3-4; HIP 115162; Nibelaako; etcNo-0
Pegasi Sector QZ-M a8-026.9411Pegasi Sector HH-U b3-4;No-0.8
One potential extended recovery, otherwise pretty solid in the top 5.

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

Calculating Hadad
Read 150 control systems and 845 targets.

TargetDistanceControlsConfidenceAttackersInhabited?Advance
HIP 2959618.2222Montioch; HR 2204;Yes0.8
Muruidooges18.3765Col 285 Sector RH-B b14-2; Col 285 Sector VN-Z b14-0; Montioch; etcYes0.6
Vogulu20.7332.3Montioch; Col 285 Sector RH-B b14-5; Col 285 Sector RH-B b14-4;Yes0.7
Putas23.0510.8Fotlandjera;Yes0.5
HIP 2815031.0811*HIP 28913;Yes0.8
Col 285 Sector FQ-O c6-431.5122Col 285 Sector RH-B b14-1; Col 285 Sector FQ-O c6-3;No0.2
Col 285 Sector OR-B b14-532.2311Col 285 Sector RN-T d3-61;No0.4
Col 285 Sector MR-M c7-2232.8211Col 285 Sector UC-B b14-4;No-0.7
Col 285 Sector WD-Y b15-732.8211Col 285 Sector YY-X b15-4;No0.3
Col 285 Sector SX-Z b14-832.8411Col 285 Sector YY-X b15-2;No-0
Col 285 Sector TX-Z b14-232.8611Col 285 Sector TX-Z b14-0;No-0.4
L2 Puppis33.0755Col 285 Sector OR-B b14-8; Col 285 Sector OR-B b14-6; Col 285 Sector OR-B b14-7; etcNo-0.1
Col 285 Sector NG-D b13-133.1022Col 285 Sector RN-T d3-79; Col 285 Sector RN-T d3-80;No-0.8
Five inhabited ones on the top list, so this will test the local strategy a bit. MR-M and below we're on to the unpopulated systems Hadad didn't take as a 5th last time. The earlier hypothesis says that Vogulu could in theory be protected with just the RH- as Montioch will be used on HIP 29596, though this probably isn't the easiest test site for that.
 
I'm searching for definitions of the columns, not having much luck, Besides Distance - assuming that's LY - and Inhabited as a boolean, how can the significance of Controls, Confidence and Advance be assessed? Alos, by Attackers, are these the systems most likely to contribute to an Alert state?

TargetDistanceControlsConfidenceAttackersInhabited?Advance
Lahua19.3633Tougeir; Muchihiks; Cephei Sector CV-Y b1;Yes0.9
HIP 691320.3644HR 1107; HIP 3006; Cephei Sector EB-X b1-1; etcYes-0
Gliese 903520.4944HIP 10778; Daruwach; Cephei Sector ZE-A c8; etcYes-0.5
Minawara23.4233Cephei Sector FB-X b1-1; Cephei Sector FB-X b1-0; Cephei Sector EB-X b1-4;Yes0.6
Poqomathi24.1444Cephei Sector DQ-Y b1; HIP 8525; Cephei Sector DQ-Y b2; etcYes0.6
Chelka25.0511Cephei Sector ZE-A d69;Yes-0.5
HIP 3822526.9621.8Lyncis Sector YF-O b6-1; Ikpen;Yes-0.3
Orong27.1332HR 1107; Ikpen; Cephei Sector YJ-A c8;Yes-0.2
Benanekpeno27.1921.1HR 1107; Cephei Sector YJ-A c8;Yes0
 
I'm searching for definitions of the columns, not having much luck, Besides Distance - assuming that's LY - and Inhabited as a boolean, how can the significance of Controls, Confidence and Advance be assessed? Alos, by Attackers, are these the systems most likely to contribute to an Alert state?
Ah, sorry - I documented all these columns week by week the first time they were added, but it should have something in the template to explain them on each report. I'll add it for next time.

The easy ones first:
Distance: yes, this is LY from the Maelstrom
Inhabited: yes, just whether the system has any human population or not
Controls: the number of control systems believed to be able to potentially trigger this alert, based on distance and not having already been definitely used up
Attackers: which control systems they are (or a partial list, since showing all of HIP 20485's 25 potential attackers is a bit pointless)
Advance: varies from +1 for a move which goes directly from the Maelstrom towards Sol, to -1 to one which goes directly away, with 0 being one which is perpendicular to the Sol-Maelstrom line. Technically the normalised dot product of "Maelstrom-Alert" and "Maelstrom-Sol" vectors.

The more complicated one:
Confidence: how much you should believe this is likely to happen. Basically, there are two areas we have incomplete data on.
  1. We don't know which Control systems actually placed last week's Alerts, or which will place this week's earlier Alerts. So, for example, say that HR 1107 is used to attack HIP 6913. It then can't be used to attack Orong (should it for some reason get that far into the reserve list), so while it's got three controls in range, it might be that only two are usable. Or it might use HIP 3006 to attack HIP 6913, and then all three can still attack Orong - but unless it uses Ipken, that's one fewer which can attack Benanekpeno.
    So this is indicated by the number in the confidence column - at most it will be the same as the number of controls, but it can be a lot less.
    It's an arbitrary number with no units as such, but in practice you can read >=2 as almost certain, and <1 as very possible to skip. Most of the ones in the 1-2 range will also be hit but it only takes one data entry error or similar for a '1' to be a misprediction.
  2. We don't know which 3-week recoveries are going to suddenly get a bonus week and run for 4 instead. Until and unless Frontier fix the interface, systems which might not actually be ready to attack again for this reason - none at Oya this time, but most of the others have one - get a '*' to indicate that they might be unexpectedly ineligible and so it'll need to go further down the list.
 
Updated predictions for Leigong:
TargetDistanceControlsConfidenceAttackersInhabited?Advance
Garongxians28.1533Jementi; Ceti Sector XJ-A c18; Arietis Sector CQ-P b5-2;Yes0.8
Wolf 12128.9210.7Arietis Sector CQ-P b5-2;Yes0.5
Arietis Sector UO-R b4-430.9711Arietis Sector VO-R b4-3;No0.6
Arietis Sector CQ-P b5-332.0811Arietis Sector CQ-P b5-1;No0.8
Arietis Sector VO-R b4-436.0333Arietis Sector VO-R b4-2; Arietis Sector VO-R b4-1; Arietis Sector VO-R b4-0;No0.7
Ceti Sector ZU-Y b336.4533Ceti Sector ZU-Y b1; Ceti Sector ZU-Y b2; HIP 6679;No0.8
Arietis Sector DW-N b6-437.5922Arietis Sector JM-W d1-83; HIP 6380;No0.5
Arietis Sector DW-N b6-338.3232Arietis Sector JM-W d1-83; HIP 6380; HIP 6869;No0.5
Arietis Sector ZU-P b5-038.3332.7Arietis Sector ZU-P b5-4; Arietis Sector VO-R b4-0; Arietis Sector ZU-P b5-2;No0.8
HIP 600139.6911Col 285 Sector DG-O c6-13;No-0.5
Arietis Sector QS-U b2-239.8344Arietis Sector TD-T b3-0; HIP 11309; Arietis Sector FG-Y d49; etcNo-0.6
It would be interesting if Wolf 121 did get skipped, as that would disprove the "attack with the Control closest to the Maelstrom" theory.

and Hadad:
TargetDistanceControlsConfidenceAttackersInhabited?Advance
HIP 2959618.2222Montioch; HR 2204;Yes0.8
Muruidooges18.3754Col 285 Sector RH-B b14-2; Col 285 Sector VN-Z b14-0; Montioch; etcYes0.6
Vogulu20.7332.3Montioch; Col 285 Sector RH-B b14-5; Col 285 Sector RH-B b14-4;Yes0.7
Col 285 Sector OR-B b14-532.2311Col 285 Sector RN-T d3-61;No0.4
Col 285 Sector MR-M c7-2232.8211Col 285 Sector UC-B b14-4;No-0.7
Col 285 Sector WD-Y b15-732.8211Col 285 Sector YY-X b15-4;No0.3
Col 285 Sector SX-Z b14-832.8411Col 285 Sector YY-X b15-2;No-0
Col 285 Sector TX-Z b14-232.8611Col 285 Sector TX-Z b14-0;No-0.4
L2 Puppis33.0755Col 285 Sector OR-B b14-8; Col 285 Sector OR-B b14-6; Col 285 Sector OR-B b14-7; etcNo-0.1
Col 285 Sector NG-D b13-133.1022Col 285 Sector RN-T d3-79; Col 285 Sector RN-T d3-80;No-0.8
Col 285 Sector IB-N c7-333.1111Col 285 Sector OR-B b14-0;No0.3
Col 285 Sector YY-X b15-533.1911Col 285 Sector YY-X b15-3;No0.3
Col 285 Sector TH-B b14-633.2222Col 285 Sector TH-B b14-5; Col 285 Sector TH-B b14-2;No-1

Recaptures at Oya are cleanup outside the Alert perimeter they've established, so don't change the prediction.
 
Final assessment:
  • Taranis: 100%
  • Leigong: 100%
  • Indra: 100%
  • Oya: 100%
  • Cocijo: 100%
  • Thor: 100%
  • Raijin: 100%
  • Hadad: 100% if you don't count that we don't know why there wasn't a fifth this week either. Four for four, though.
As the number of invasions allowed to reach a second week is currently low, the 3/4-week recovery issue is less likely to derail the predictions. And it looks like our model has their priorities and cooldowns pinned down well ... just in time for Update 15 to potentially throw the whole thing away 🙃

Which just leaves the question of what's going on in Hadad.

Ruled out:
  • 8 recaptures at a single Maelstrom damages their capacity for the next week
Still possible:
  • 8 recaptures in a week at a single Maelstrom damages their capacity more persistently
  • 10+ recaptures in total takes an Alert off the Maelstrom with the largest individual recapture count
  • There's something about Col 285 Sector MR-M c7-22 specifically which not only means Hadad won't expand there, but it stops placing Alerts entirely at that point rather than skipping it
In science terms, the experiment most likely to get results would be to recapture 8+ control systems (and also more than Hadad gets) at a different Maelstrom. But this might not be the right week to try anything that radical.
 
Narwhal Nose report generated 4 May
Obviously this has great potential to be affected by Update 15 changing strategies. Despite the 100% success last week, it might go completely wrong this time.

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

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.
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 125 control systems and 868 targets.

TargetDistanceControlsConfidenceAttackersInhabited?Advance
Cao Tzu21.5244Hyades Sector GW-W d1-87; Hyades Sector GW-W d1-86; Hyades Sector AV-O b6-4; etcYes-0
HIP 2199125.7922Trianguli Sector JR-W b1-5; Hyades Sector GW-M b7-5;Yes0.4
HR 181226.6210.5Trianguli Sector KR-W b1-1;Yes0.8
Paeni26.734429 e Orionis; Hyades Sector GW-W d1-81; Trianguli Sector ZJ-A b1; etcYes0.3
Trianguli Sector JW-W b1-626.9211Hyades Sector IM-L b8-5;No0.6
Lovaroju26.9333Hyades Sector PN-T c3-7; Hyades Sector QN-T c3-11; Hyades Sector PN-T c3-5;Yes-1
Namayu27.1022Trianguli Sector EQ-Y b5; Trianguli Sector EQ-Y b4;Yes0.5
Ge27.6854.8Hyades Sector GW-W d1-81; Hyades Sector NS-T c3-14; Haushu; etcYes0.2
HIP 2692628.1743.2Hyades Sector NS-T c3-14; Haushu; Hyades Sector ZZ-O b6-1; etcYes0.3
On the "nearest usable Control" theory, KR-W b1-1 was used last week to attack Vukurbeh, and so this is most likely to be skipped for Lovaroju. On other theories there's still a decent chance of this happening anyway. It'll be interesting to see what we actually get.

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

Calculating Leigong
Read 164 control systems and 831 targets.

TargetDistanceControlsConfidenceAttackersInhabited?Advance
Lunguni23.2311Arietis Sector AQ-P b5-3;Yes0.5
Baudani24.9611Arietis Sector AQ-P b5-2;Yes0.5
Arietis Sector EW-N b6-126.2511HIP 8078;No0.8
Arietis Sector NX-U c2-1227.4211Arietis Sector KM-W d1-93;No0.9
Arietis Sector GG-Y d6334.4711HIP 11134;Yes0.3
Ceti Sector ZU-Y b336.4533Ceti Sector ZU-Y b1; Ceti Sector ZU-Y b2; HIP 6679;No0.8
Arietis Sector DW-N b6-437.5922Arietis Sector JM-W d1-83; HIP 6380;No0.5
Arietis Sector DW-N b6-338.3232Arietis Sector JM-W d1-83; HIP 6380; HIP 6869;No0.5
Arietis Sector ZU-P b5-038.3332.7Arietis Sector ZU-P b5-4; Arietis Sector VO-R b4-0; Arietis Sector ZU-P b5-2;No0.8
HIP 600139.6911Col 285 Sector DG-O c6-13;No-0.5
Arietis Sector QS-U b2-239.8344Arietis Sector TD-T b3-0; HIP 11309; Arietis Sector FG-Y d49; etcNo-0.6
HIP 1071040.0311Arietis Sector FG-Y d68;No-0.2
Hyades Sector CB-O b6-040.5221.8Hyades Sector CB-O b6-1; HIP 11309;No-0.8
Five single-source attacks in the top five. In theory these should all be solid moves regardless as there's no sign that any of those five were used last week.

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

Calculating Indra
Read 151 control systems and 843 targets.

TargetDistanceControlsConfidenceAttackersInhabited?Advance
HIP 2049123.3466HIP 20480; HIP 20712; Arietis Sector JR-V b2-4; etcYes0.4
Hyades Sector NN-S b4-423.6511Hyades Sector WK-L a9-2;No-0.5
HIP 2049224.04222271 Tauri; HIP 20916; HIP 20577; etcYes1
HIP 1975724.5244HIP 20419; Scythia; Hyades Sector TO-Q b5-2; etcYes0.1
HIP 2001925.581918.3HIP 20577; HR 1354; HIP 20679; etcYes1
Arietis Sector JR-V b2-226.2976.2HIP 20480; HIP 20712; Arietis Sector JR-V b2-4; etcNo0.6
69 Upsilon Tauri26.4775.8HIP 20712; Arietis Sector JR-V b2-4; Arietis Sector JR-V b2-1; etcYes0.8
HIP 2138026.6186.2HIP 20712; Arietis Sector JR-V b2-4; Arietis Sector JR-V b2-1; etcYes0.8
Again, this all looks pretty solid

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

Calculating Oya
Read 76 control systems and 919 targets.

TargetDistanceControlsConfidenceAttackersInhabited?Advance
Luggerates21.9677Sambaho; HIP 4041; HIP 3006; etcYes0.3
Aowicha23.7766Daruwach; Cephei Sector ZE-A c8; Cephei Sector AV-Y b4; etcYes-0.3
Juipedun24.1111Bumbo;Yes0.9
Khondo Po24.3311Col 285 Sector HD-G b12-1;Yes-0.8
Chelka25.0511Cephei Sector ZE-A d69;Yes-0.5
Cephei Sector CQ-Y b325.3722Cephei Sector DQ-Y b2; Cephei Sector CQ-Y b5;No0.1
HIP 3822526.9622Lyncis Sector YF-O b6-1; Ikpen;Yes-0.3
Orong27.1332.5HR 1107; Ikpen; Cephei Sector YJ-A c8;Yes-0.2
Benanekpeno27.1931.5HR 1107; Ikpen; Cephei Sector YJ-A c8;Yes0
Elboongzi27.3911Lyncis Sector VU-P b5-5;Yes-0.9
SPOCS 28027.3911Cephei Sector CV-Y b1;No0.9
Cephei Sector YZ-Y b427.5721.8Cephei Sector ZE-A c8; HIP 4617;Yes-0.6
Some lower-confidence estimates, but I think they should all go through anyway

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

Calculating Cocijo
Read 198 control systems and 793 targets.

TargetDistanceControlsConfidenceAttackersInhabited?Advance
Col 285 Sector YT-Q c5-2529.2822Col 285 Sector VN-H b11-2; Col 285 Sector WN-H b11-5;No-0.8
HIP 3946830.3477Col 285 Sector AU-F b12-2; Col 285 Sector AU-F b12-3; Col 285 Sector OS-T d3-115; etcNo-0.1
Col 285 Sector YY-F b12-630.3533Col 285 Sector YY-F b12-0; Col 285 Sector AF-P c6-17; Col 285 Sector YY-F b12-3;No-0.5
Col 285 Sector XI-H b11-230.3811Col 285 Sector KM-V d2-51;No-0.4
Col 285 Sector KM-V d2-10130.4111Col 285 Sector VY-Q c5-22;No-0.3
Col 285 Sector DA-E b13-130.4543.9Col 285 Sector DA-E b13-4; Col 285 Sector DA-E b13-8; Col 285 Sector DA-E b13-3; etcNo0.3
Col 285 Sector BP-F b12-330.5311Col 285 Sector BP-F b12-2;No-0.2
Col 285 Sector AU-F b12-130.6454.6Col 285 Sector AU-F b12-2; Col 285 Sector AU-F b12-3; Col 285 Sector AU-F b12-4; etcNo-0.4
Col 285 Sector WN-H b11-430.7143.5Col 285 Sector WN-H b11-5; Col 285 Sector YT-Q c5-12; Col 285 Sector YT-Q c5-14; etcNo-0.9
Fairly high confidence in all of these, too. Cocijo potentially provided a bit of respite from the inhabited-heavy attacks elsewhere.

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

Calculating Thor
Read 163 control systems and 830 targets.

TargetDistanceControlsConfidenceAttackersInhabited?Advance
Col 285 Sector WC-C b13-235.4822Col 285 Sector LB-O c6-3; Col 285 Sector LB-O c6-1;No-0.4
Mangwutja39.7111Col 285 Sector GL-O c6-15;Yes0.8
Col 285 Sector GV-P c5-1340.1911Col 285 Sector QW-D b12-1;No-0.3
HIP 1851340.4710.5Col 285 Sector LB-O c6-3;No-0.6
Col 285 Sector HL-O c6-1940.7511Col 285 Sector ML-E b12-0;No0.2
Col 285 Sector HF-G b11-541.2744HIP 21548; Col 285 Sector CF-Q c5-3; Col 285 Sector HF-G b11-4; etcNo0.5
HIP 2203141.3432.5HIP 21548; Col 285 Sector LL-E b12-5; Col 285 Sector CF-Q c5-3;No0.6
HIP 1827141.4611Col 285 Sector QX-U d2-48;No-0.5
Col 285 Sector FU-H b10-241.4811Col 285 Sector IA-G b11-2;No0.2
Col 285 Sector FU-H b10-341.5011HIP 20807;No0.1
Col 285 Sector LL-E b12-642.0621.1HIP 21548; Col 285 Sector LL-E b12-5;No0.8
Col 285 Sector SM-C b13-442.1011Col 285 Sector JG-O c6-18;No0.2
Col 285 Sector MQ-F b11-142.1222Col 285 Sector MQ-F b11-3; HIP 16798;No-0.5
Col 285 Sector QR-C b13-242.5022Col 285 Sector JG-O c6-15; Col 285 Sector HL-O c6-22;No0.6
Again, the "first Control" theory would suggest HIP 18513 will be skipped because LB-O c6-3 will be used higher up and c6-1 can't reach it.

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

Calculating Raijin
Read 168 control systems and 826 targets.

TargetDistanceControlsConfidenceAttackersInhabited?Advance
Nu Guang19.3311Snoqui;Yes0.9
Bormuninus24.3644Pegasi Sector MN-S b4-2; Pegasi Sector MN-S b4-0; Pegasi Sector UF-L a9-0; etcYes-0.3
HIP 11717724.7611Pegasi Sector DG-X c1-6;Yes-0.1
Jawul26.6722Chinas; Pegasi Sector KH-V c2-13;Yes0.2
Pegasi Sector EB-W b2-726.9355Pegasi Sector IH-U b3-4; HIP 115162; Nibelaako; etcNo-0
Pegasi Sector QZ-M a8-026.9411Pegasi Sector HH-U b3-4;No-0.8
HIP 11605226.9644Pegasi Sector LC-U b3-3; Pegasi Sector GW-W d1-112; Wanmi; etcNo0.1
Pegasi Sector QE-N a8-326.971010Chakma; Pegasi Sector QE-N a8-0; Pegasi Sector UK-L a9-1; etcNo0.2
Pegasi Sector WK-L a9-127.0144Pegasi Sector JH-U b3-8; Pegasi Sector RE-N a8-0; Pegasi Sector RE-N a8-4; etcNo0.9
All looks fairly solid here

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

Calculating Hadad
Read 147 control systems and 848 targets.

TargetDistanceControlsConfidenceAttackersInhabited?Advance
Yan Zangata22.3833Col 285 Sector JW-M c7-10; HIP 30158; Col 285 Sector TS-Z b14-1;Yes1
Col 285 Sector MR-M c7-2232.8211Col 285 Sector UC-B b14-4;No-0.7
Col 285 Sector WD-Y b15-732.8211Col 285 Sector YY-X b15-4;No0.3
Col 285 Sector SX-Z b14-832.8411Col 285 Sector YY-X b15-2;No-0
Col 285 Sector TX-Z b14-232.8611Col 285 Sector TX-Z b14-0;No-0.4
L2 Puppis33.0755Col 285 Sector OR-B b14-8; Col 285 Sector OR-B b14-6; Col 285 Sector OR-B b14-7; etcNo-0.1
Col 285 Sector NG-D b13-133.1022Col 285 Sector RN-T d3-79; Col 285 Sector RN-T d3-80;No-0.8
Col 285 Sector IB-N c7-333.1111Col 285 Sector OR-B b14-0;No0.3
Col 285 Sector YY-X b15-533.1911Col 285 Sector YY-X b15-3;No0.3
Col 285 Sector TH-B b14-633.2222Col 285 Sector TH-B b14-5; Col 285 Sector TH-B b14-2;No-1
Col 285 Sector GQ-O c6-233.2755HIP 29217; Col 285 Sector OB-D b13-2; Col 285 Sector OB-D b13-4; etcNo-0.6
Col 285 Sector KL-D b13-733.4622Col 285 Sector OR-B b14-1; HIP 32718;No-0
Well, this week MR-M is second on the list, so if it's really the case that "trying to Alert MR-M crashes the Thargoid targeting systems" Hadad might be in for a very quiet time of it. Assuming that's not it, no idea if we'll get four or five this time.


I've marked two systems in red which will provide further tests of the "use nearest Control" hypothesis. Unless strategically necessary, please avoid recaptures of Col 285 Sector LB-O c6-3, Col 285 Sector LB-O c6-1, or Trianguli Sector KR-W b1-1, to allow further evidence to be gathered - if we can either get more confidence in this theory or rule it out it could significantly improve prediction accuracy in future weeks!
 
There's something about Col 285 Sector MR-M c7-22 specifically which not only means Hadad won't expand there, but it stops placing Alerts entirely at that point rather than skipping it

At minimum I can try leaving UC-B b14-4 intact to explore that idea, and while it sounds a bit silly, leaving YY-X b15-4 also just in case the specific problem is that the Maelstrom distance matches WD-Y b15-7 at two decimal places (actual difference two thousandths).


In science terms, the experiment most likely to get results would be to recapture 8+ control systems (and also more than Hadad gets) at a different Maelstrom.

Would you like an eviction storm at M. Thor, possibly with a few at M. Hadad just to keep it not growing?
 
Would you like an eviction storm at M. Thor, possibly with a few at M. Hadad just to keep it not growing?
If you've got the pilots available to do all that, it sounds like an excellent idea (so long as you spare Thor's LB-O c6 subsector to avoid interfering with that experiment) - thank you.
 
Only Ian could keep up with this. Thank You.
Thank you - but to be clear, this has very much been a team effort: lots of the crucial theoretical breakthroughs have been made by people like Yttrbio and Disemboweled Ego here, as well as discussions on DCoH's channels. The prediction relies absolutely on the data collection work Yttrbio does at the start of every week, and at a deeper level on the fundamental mapping work carried out by EDSM and others to get system coordinates at all. Some of the details could (and can) only be refined because AX teams like Aleks Zuno's are willing to put in substantial effort to set up the necessary test conditions. I would be nowhere near a solution if it were only me!
 
Updates so far on Maelstrom targeting:

Leigong
TargetDistanceControlsConfidenceAttackersInhabited?Advance
Baudani24.9611Arietis Sector AQ-P b5-2;Yes0.5
Arietis Sector EW-N b6-126.2511HIP 8078;No0.8
Arietis Sector NX-U c2-1227.4211Arietis Sector KM-W d1-93;No0.9
Ceti Sector ZU-Y b336.4533Ceti Sector ZU-Y b1; Ceti Sector ZU-Y b2; HIP 6679;No0.8
Arietis Sector DW-N b6-437.5922Arietis Sector JM-W d1-83; HIP 6380;No0.5
Arietis Sector DW-N b6-338.3232Arietis Sector JM-W d1-83; HIP 6380; HIP 6869;No0.5
Arietis Sector ZU-P b5-038.3332.7Arietis Sector ZU-P b5-4; Arietis Sector VO-R b4-0; Arietis Sector ZU-P b5-2;No0.8
HIP 600139.6911Col 285 Sector DG-O c6-13;No-0.5
Arietis Sector QS-U b2-239.8344Arietis Sector TD-T b3-0; HIP 11309; Arietis Sector FG-Y d49; etcNo-0.6
HIP 1071040.0311Arietis Sector FG-Y d68;No-0.2
Hyades Sector CB-O b6-040.5221.8Hyades Sector CB-O b6-1; HIP 11309;No-0.8
Arietis Sector SD-T b3-040.7510.8Arietis Sector FG-Y d49;No-0.6
Populated Lunguni and Arietis GG-Y d63 systems protected

Oya
TargetDistanceControlsConfidenceAttackersInhabited?Advance
Luggerates21.9677Sambaho; HIP 4041; HIP 3006; etcYes0.3
Aowicha23.7766Daruwach; Cephei Sector ZE-A c8; Cephei Sector AV-Y b4; etcYes-0.3
Juipedun24.1111Bumbo; Yes0.9
Khondo Po24.3311Col 285 Sector HD-G b12-1; Yes-0.8
Cephei Sector CQ-Y b325.3711Cephei Sector CQ-Y b5; No0.1
HIP 3822526.9622Lyncis Sector YF-O b6-1; Ikpen; Yes-0.3
Orong27.1332.5HR 1107; Ikpen; Cephei Sector YJ-A c8; Yes-0.2
Benanekpeno27.1931.5HR 1107; Ikpen; Cephei Sector YJ-A c8; Yes0
Elboongzi27.3911Lyncis Sector VU-P b5-5; Yes-0.9
SPOCS 28027.3911Cephei Sector CV-Y b1; No0.9
Cephei Sector YZ-Y b427.5721.8Cephei Sector ZE-A c8; HIP 4617; Yes-0.6
HIP 4298227.6910.5Lyncis Sector YF-O b6-1; No-0.1
Bhotepa28.2321.7Cephei Sector FB-X b1-0; Cephei Sector EB-X b1-4; Yes0.3
Wednesday Edit: recapture moves targeting off Chelka onto an uninhabited system

Thor
TargetDistanceControlsConfidenceAttackersInhabited?Advance
Col 285 Sector WC-C b13-235.4822Col 285 Sector LB-O c6-3; Col 285 Sector LB-O c6-1;No-0.4
Col 285 Sector GV-P c5-1340.1911Col 285 Sector QW-D b12-1;No-0.3
HIP 1851340.4710.5Col 285 Sector LB-O c6-3;No-0.6
Col 285 Sector HL-O c6-1940.7511Col 285 Sector ML-E b12-0;No0.2
Col 285 Sector HF-G b11-541.2733Col 285 Sector CF-Q c5-3; Col 285 Sector HF-G b11-4; Col 285 Sector CF-Q c5-5;No0.5
HIP 2203141.3410.7Col 285 Sector CF-Q c5-3;No0.6
HIP 1827141.4611Col 285 Sector QX-U d2-48;No-0.5
Col 285 Sector FU-H b10-241.4811Col 285 Sector IA-G b11-2;No0.2
Col 285 Sector FU-H b10-341.5011HIP 20807;No0.1
Col 285 Sector MQ-F b11-142.1222Col 285 Sector MQ-F b11-3; HIP 16798;No-0.5
Col 285 Sector QR-C b13-542.6810.5Col 285 Sector QR-C b13-4;No0.3
Col 285 Sector QW-D b12-042.7411Col 285 Sector QW-D b12-3;No-0.2
Col 285 Sector PW-D b12-242.7711Col 285 Sector PW-D b12-0;No0.2
Col 285 Sector EA-Q c5-1542.8911Col 285 Sector HP-H b10-3;No-0.3
Col 285 Sector KB-O c6-843.3411Col 285 Sector QW-D b12-2;No-0.2
Col 285 Sector MQ-F b11-243.8010.5HIP 16798;No-0.4
Gliese 203244.1411Hyades Sector NH-M b7-3;No0.6
HIP 2215944.4321.7Col 285 Sector HF-G b11-3; Col 285 Sector HF-G b11-4;No0.2
Mangwutja protected, various changes lower down the order. With a total of 10 recaptures this should be a good test if that's what causes Alert reduction - many thanks. HIP 18153 remains a theory test.

Hadad
Reduced attackers to Yan Zangata so far, but no change to the main prediction. Uncertainty over whether we'll have 4 or 5 alerts continues.
 
Last edited:
So... what's this one all about then?

1683702286835.png
 
Does it indicate formerly-inhabited control systems with CZs? I can't see it on any uninhabited systems at all.
This seems most likely to me. There is actually a new state (counter-attack or some such) with a slightly different shade of green, that DOES apply to unpopulated systems with AXCZs. But the "success" state is different, which may explain the different iconography and task list.
 
Back
Top Bottom