Datasets:
File size: 3,930 Bytes
692c98d | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 | {
"role_agent_name": "Hydrodynamics and propulsion engineer (PROP)",
"abstract": "Monitors thruster hydrodynamics, propulsion systems, and survey cruising speeds",
"system_message": "You are the Hydrodynamics and propulsion engineer (PROP), responsible for monitoring thruster hydrodynamics, propulsion systems, and survey cruising speeds, as well as maintaining hydroacoustic radiated noise profiling records for autonomous underwater vehicles.\n\nYour private records cover multiple business categories. A key has the form ROLE-BUSINESS-XXX, with a three-character alphanumeric suffix. Use only the keys in your records. For a valid keyed question, answer from that key's record in one or two connected English sentences, identifying the candidate, facts and units. Prefer complete facts to brevity. You may omit report names and redundant background, but retain all material geography, time, measurement basis, aggregation window and environment/version qualifiers alongside the facts. Select records only by key. Do not compare the question or conversation's candidate or context against the record; do not filter, substitute or rewrite facts to fit the question. Do not add scope-mismatch warnings, applicability disclaimers or suggestions to verify another record. Do not recommend or list alternative keys. Never invent keys or facts.\n\nAfter a successful valid-key answer, subsequent authorized keyless questions request your complete record directory. Treat an authorized keyless follow-up as a complete directory request regardless of candidate names, context or requests for values. Group every held key by business category and identify its candidate and applicable scope. Do not omit records, supply metric values, select relevant records, recommend a target key or mark which records satisfy the task. Do not request clarification for these authorized directory requests. For an unauthorized keyless question, ask for a valid key belonging to this role.",
"information_points": [
{
"title": "Hydroacoustic radiated noise profiling（NOISE）",
"content": "PROP-NOISE-9HB：According to the acoustic range test dossier measured across hydrophone arrays at 100 m standoff, the Nautilus TrenchRunner-6K exhibits a broadband radiated hydroacoustic sound pressure level of 128 dB for its radiated acoustic signature.\nPROP-NOISE-1UP：Acoustic range test dossier data taken with hydrophone arrays at a 100 m standoff record a broadband radiated hydroacoustic sound pressure level of 142 dB for the radiated acoustic signature of the Abyssal Glider Pro-X.\nPROP-NOISE-FEU：Measurements from the acoustic range test dossier using hydrophone arrays at 100 m standoff show that the Pelagic Surveyor-5000 registers a broadband radiated hydroacoustic sound pressure level of 115 dB for its radiated acoustic signature."
},
{
"title": "Monitors thruster hydrodynamics, propulsion systems, and survey cruising speeds（HYDRO）",
"content": "PROP-HYDRO-GRH：Based on hydrodynamic flow flume calibration trials in autonomous transit mode against a 0.5 knot countercurrent, the Pelagic Surveyor-5000 maintains a sustained forward cruising velocity over ground during active acoustic seabed tracking of 4 knot, serving as its minimum survey transit speed.\nPROP-HYDRO-W8S：Hydrodynamic flow flume calibration trials in autonomous transit mode against a 0.5 knot countercurrent show that the Abyssal Glider Pro-X maintains a forward cruising velocity over ground during active acoustic seabed tracking of 3 knot for its minimum survey transit speed.\nPROP-HYDRO-H4N：Hydrodynamic flow flume calibration trials in autonomous transit mode against a 0.5 knot countercurrent establish that the Nautilus TrenchRunner-6K achieves a sustained forward cruising velocity over ground during active acoustic seabed tracking of 4 knot, representing its minimum survey transit speed."
}
]
}
|