mnit-rtmc / iris Goto Github PK

The sign_event table has a msg_owner column, which contains the "owner" of a sign message when activated. After a scheduled message is cleared, the user msg (msg_user) will be activated, with msg_owner set to the user who created that message. This can be confusing if the message is "blank" -- it seems like the user initiated the sign to blank, but in fact, it was just a regular scheduled message expiring with no user interaction.

The fix is to not store blank messages in DMS msg_user

Manual or automatic?

When used, populate line selectors with downstream pickable locations. Use the same logic as incident locators.

If a message is sent by an external NTCIP system, IRIS can't display any included graphics.

Newer firmware compatibility

When a whole-sign text rectangle tag is used in a multi-page message pattern in the message composer, IRIS will insert the text from the composer fields incorrectly, leading to overlapping text on one page of the message, and leaving other page(s) blank. For example, using the following message pattern:

[tr1,1,0,0][np][tr1,1,0,0]

will produce:

TEST 1[nl]TEST 2[nl]TEST 3[tr1,1,0,0]TEST 4[nl]TEST 5[nl]TEST 6[np][nl][nl][tr1,1,0,0]

Looking like this in the preview and on the sign:

Page 1	Page 2

This does not occur without the [tr...] tags, for example:

[np]

produces:

TEST 1[nl]TEST 2[nl]TEST 3[np]TEST 4[nl]TEST 5[nl]TEST 6

Which looks like:

Page 1	Page 2

Interestingly, this behavior also does not appear when using a non-default font tag. For example:

[fo10][tr1,1,0,0][np][tr1,1,0,0]

produces:

[fo10][tr1,1,0,0]TEST 1[nl]TEST 2[nl]TEST 3[np]TEST 4[nl]TEST 5[nl]TEST 6[tr1,1,0,0]

And looks like:

Page 1	Page 2

When using the default font in a font tag, however, it produces the issue (like the first pair of images). In that case, this message pattern:

[fo11][tr1,1,0,0][np][tr1,1,0,0]

produces the following MULTI string:

TEST 1[nl]TEST 2[nl]TEST 3[fo11][tr1,1,0,0]TEST 4[nl]TEST 5[nl]TEST 6[np][nl][nl][tr1,1,0,0]

This behavior has been observed in several versions back to at least 5.42.2 and can be replicated in the current version (5.49.0). Hopefully it is just a minor error in handling the input from the composer fields. If you have any questions or would like more testing, just let me know.

For beacons attached to "slippery when flashing" signs -- when nearby weather sensors report friction threshold below 0.6 (configurable).

This issue tracks tasks needed to finish the MVP (minimum viable product) Web UI.

Mapping

• Change earthwyrm to use rosewood/loam instead of PostGIS
• Update to modern version of Leaflet JS library
• Replace Leaflet.VectorGrid plugin with VectorTileLayer
• Handle Leaflet events by updating selected items, etc.
• Add tooltips for devices

DMS

• Change card background color based linked incident type
• Generate map layer loam file on configuration changes
• Allow free-form text entry for users with permissions
• Find other required features from Java UI

Honeybee / graft

• Merge into a single service, using axum
• Generate freeway segment layer (loam) for earthwyrm
• Implement SSE messages for selected card / resource type
• Verify user's network domain on login

Ideas:

• Show name of user who created lock
• Initial lock rate should match current ramp demand
• Add duration, defaulted to 15 minutes
• Automatic queue override to prevent backup
• Lock reasons: knocked down, indication

Hi, I just finished installing and trying to run IRIS, but it errors out after I used the given credentials of admin/atms_242.

Any insight on how to fix this?
----ERROR----
us.mn.state.dot.sonar.SonarException: Login timed out
at us.mn.state.dot.sonar.client.Client.waitLogin(Unknown Source)
at us.mn.state.dot.sonar.client.Client.login(Unknown Source)
at us.mn.state.dot.tms.client.SonarState.login(Unknown Source)
at us.mn.state.dot.tms.client.IrisClient.createSession(Unknown Source)
at us.mn.state.dot.tms.client.IrisClient.access$300(Unknown Source)
at us.mn.state.dot.tms.client.IrisClient$4.doInBackground(Unknown Source)
at us.mn.state.dot.tms.client.IrisClient$4.doInBackground(Unknown Source)
at javax.swing.SwingWorker$1.call(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at javax.swing.SwingWorker.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

Use hashtags for signs, action plans, cameras. Need to allow creating/deleting resources.

Allow sign configs to share brightness tables.

When deploying a DMS message from an incident, Operate permission (DMS/incident) should be sufficient for the suggested message.

Currently, the location (2nd line) must match an existing msg_line in the sign's library.

Attempting to add a DMS to a new installation, following the step-by-step on the web page I enter a name for the comm link and when I click create it doesn't appear in the table as indicated in the step-by-step it appears to just vanish

Hello

The tutorial in the site https://mnit-rtmc.github.io/iris/mapping.html, explaining how generate maps for iris is obsolete.
A lot of files required are no longer available on internet.

Can you update this part please.

Thank you in advance.

Uncompressed 24-bit images in base-64 can be large.

Currently, external authentication is only supported using unencrypted connections to an LDAP server, such as Active Directory. LDAPS would improve security of these connections.

The label column in detector_view is generated automatically. If the cross-street is NULL, it shows "FUTURE", even if there is a landmark.

Add a method to send anti-aliased text messages as dynamically generated graphics. Use Red Hat's overpass font. Open questions:

1. Should a new MULTI-like tag be added to support this?
2. How should this interact with the message composer?
3. Font management?

• Static .png background
• Rectangle defining location of DMS on sign (x,y,w,h)
• Add support in honeybee as well as IRIS java

Features:

• Crack attempt detection
• Request throttling (minimum 1 second)
• Forced password reset on login (non-LDAP accounts)
• Track hashes of compromised passwords and prevent reuse
• Auto-disable accounts based on inactivity
• Reduced permission account management
• Notes field on user (for admin)

If stamp marks end of period, should it be minus operator here, not plus?
But I may be wrong.

And by the way, you can use Long.compare() method.

Maybe these should only be allowed with "Manage" permissions?

1. Replace streamable flag with "#Streamable" hashtag
2. Also for "#Publish" ?
3. Tag for "#IrisOnly" / "#NoVdu" ?
4. Others?

Add a hashtags field to the "camera" / "camera_pub" JSON files produced by honeybee.

• Exit ramp incidents
• Add "extend range" button to deploy dialog
• LCS indications are not associated with incident
• DMS deployment should not require free-form permissions

Add maintenance style when "Too many stuck pixel..." error happens

See https://mnit-rtmc.github.io/iris/message_patterns.html#message-combining

Colors imported as RGB instead of BGR

• turn on
• turn off
• add / clear lock