[Logged] SOSUS-calculated uncertainty areas (1147.14)

Matrix Games Forums

Forums Register Login Photo Gallery Member List Search Calendars FAQ

My Profile Inbox Address Book My Subscription My Forums Log Out

[Logged] SOSUS-calculated uncertainty areas (1147.14)

View related threads: (in this forum | in all forums)

Logged in as: Guest

Users viewing this topic: none

Printable Version

All Forums >> [New Releases from Matrix Games] >> Command: Modern Operations series >> Tech Support >> [Logged] SOSUS-calculated uncertainty areas (1147.14)

Page: [1]

Message

<< Older Topic Newer Topic >>

[Logged] SOSUS-calculated uncertainty areas (1147.14) - 2/24/2021 10:13:36 AM

Gus112GR

Posts: 11
Joined: 10/6/2014
From: Athens, Greece
Status: offline

I decided to fire up Northern Inferno once again in CMO (had completed this before in CMANO) just to see the evolution of certain game mechanics and although the sonar/sound propagation model seems to be more realistic as it is now much harder to detect enemy submarines, there is something odd about how SOSUS works and how the uncertainty areas are calculated for subsurface contacts.

In the attached save file the calculated uncertainty areas for several submarines are quite wide, spanning across several hundred nautical miles, which makes the formulation of a suitable strategy to localize these contacts nearly impossible. In addition, some of these areas appear to be either entirely over land or covered in large by land mass (e.g. PL-611 Zulu IV over Greenland).

In certain instances, SOSUS was able to define the position of a sub with a relatively low uncertainty (ASW PZ1 for K-387) but a few moments later the uncertainty massively increases with the estimated location of the sub contact teleporting several hundred nm away (see the current, recalculated uncertainty area for K-387).

This behavior has some serious implications on ASW patrol missions. Aircraft trying to prosecute a contact will instantly re-direct themselves to the boundaries of the new uncertainty area (which might be, as described above, distinct from the original location), effectively defeating the purpose of setting up ASW patrol missions as user input/micromanagement is required to override aircraft behavior (see for example Nimrod MR.1 assigned to ASW PZ1).

Attachment (1)

< Message edited by Rory Noonan -- 2/25/2021 4:29:55 AM >

Post #: 1

RE: SOSUS-calculated uncertainty areas (1147.14) - 2/25/2021 4:29:40 AM

WSBot

Posts: 182
Joined: 1/17/2021
Status: offline

0014424

(in reply to Gus112GR)

Post #: 2

RE: SOSUS-calculated uncertainty areas (1147.14) - 3/4/2021 11:49:11 AM

Gus112GR

Posts: 11
Joined: 10/6/2014
From: Athens, Greece
Status: offline

Not sure if this is related to the original post but SOSUS was eventually able to get a fairly good fix on K-387. The sub is (reportedly) doing 5kts at a depth of 131ft but none of my active sensors (active buoys or dipping sonar) will pick it up. In all cases the predicted location of the sub is well within sensor range.

Assuming the active sensors are working ok and there�s nothing wrong with the acoustic signature of this specific sub class, it looks like SOSUS is unable to reliably determine the general location of a sub.

Attachment (1)

(in reply to WSBot)

Post #: 3

RE: SOSUS-calculated uncertainty areas (1147.14) - 4/24/2021 2:40:18 PM

AndrewJ

Posts: 2318
Joined: 1/5/2014
Status: offline

Here's an example using the revised sonar model (1147.21)

The SOSUS system can only detect the subs at a range of about 50 to 60 miles, but displays uncertainty zones as if they were hundreds of miles away.

Unless the player has run tests to understand how the SOSUS actually performs, this can seriously mislead them about the position of the subs, and the automated AI has no chance to recognize the situation. Units on ASW patrol missions can be lead well out of position as a result.

Attachment (1)

(in reply to Gus112GR)

Post #: 4

RE: SOSUS-calculated uncertainty areas (1147.14) - 4/29/2021 1:14:06 PM

Dimitris

Posts: 13282
Joined: 7/31/2005
Status: offline

Can you please check with B1147.22 .

_____________________________

Facebook
Twitter

(in reply to AndrewJ)

Post #: 5

RE: SOSUS-calculated uncertainty areas (1147.14) - 4/30/2021 9:26:37 PM

AndrewJ

Posts: 2318
Joined: 1/5/2014
Status: offline

I tried with B1147.22.

Detection ranges have significantly increased, however there can still be a large amount of variation in the displayed position of the sub.

In this example, some contacts are displayed exactly on the actual position of the sub, some are displayed ~ 185 miles short of of the actual position, and others are up to 500 miles long of the actual sub.

Attachment (1)

(in reply to Dimitris)

Post #: 6

Page: [1]

All Forums >> [New Releases from Matrix Games] >> Command: Modern Operations series >> Tech Support >> [Logged] SOSUS-calculated uncertainty areas (1147.14)

Page: [1]