Dataset Preview
Duplicate
The full dataset viewer is not available (click to read why). Only showing a preview of the rows.
The dataset generation failed
Error code:   DatasetGenerationError
Exception:    CastError
Message:      Couldn't cast
ok: bool
input: string
record_count: int64
clean_count: int64
train_count: int64
val_count: int64
warnings: list<item: null>
  child 0, item: null
outputs: struct<train: string, val: string>
  child 0, train: string
  child 1, val: string
confidence: double
instruction: string
context: string
source: string
tags: list<item: string>
  child 0, item: string
output: string
to
{'instruction': Value('string'), 'input': Value('string'), 'context': Value('string'), 'output': Value('string'), 'tags': List(Value('string')), 'source': Value('string'), 'confidence': Value('float64')}
because column names don't match
Traceback:    Traceback (most recent call last):
                File "/usr/local/lib/python3.12/site-packages/datasets/builder.py", line 1872, in _prepare_split_single
                  for key, table in generator:
                                    ^^^^^^^^^
                File "/usr/local/lib/python3.12/site-packages/datasets/packaged_modules/json/json.py", line 260, in _generate_tables
                  self._cast_table(pa_table, json_field_paths=json_field_paths),
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
                File "/usr/local/lib/python3.12/site-packages/datasets/packaged_modules/json/json.py", line 120, in _cast_table
                  pa_table = table_cast(pa_table, self.info.features.arrow_schema)
                             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
                File "/usr/local/lib/python3.12/site-packages/datasets/table.py", line 2272, in table_cast
                  return cast_table_to_schema(table, schema)
                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
                File "/usr/local/lib/python3.12/site-packages/datasets/table.py", line 2218, in cast_table_to_schema
                  raise CastError(
              datasets.table.CastError: Couldn't cast
              ok: bool
              input: string
              record_count: int64
              clean_count: int64
              train_count: int64
              val_count: int64
              warnings: list<item: null>
                child 0, item: null
              outputs: struct<train: string, val: string>
                child 0, train: string
                child 1, val: string
              confidence: double
              instruction: string
              context: string
              source: string
              tags: list<item: string>
                child 0, item: string
              output: string
              to
              {'instruction': Value('string'), 'input': Value('string'), 'context': Value('string'), 'output': Value('string'), 'tags': List(Value('string')), 'source': Value('string'), 'confidence': Value('float64')}
              because column names don't match
              
              The above exception was the direct cause of the following exception:
              
              Traceback (most recent call last):
                File "/src/services/worker/src/worker/job_runners/config/parquet_and_info.py", line 1347, in compute_config_parquet_and_info_response
                  parquet_operations = convert_to_parquet(builder)
                                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^
                File "/src/services/worker/src/worker/job_runners/config/parquet_and_info.py", line 980, in convert_to_parquet
                  builder.download_and_prepare(
                File "/usr/local/lib/python3.12/site-packages/datasets/builder.py", line 884, in download_and_prepare
                  self._download_and_prepare(
                File "/usr/local/lib/python3.12/site-packages/datasets/builder.py", line 947, in _download_and_prepare
                  self._prepare_split(split_generator, **prepare_split_kwargs)
                File "/usr/local/lib/python3.12/site-packages/datasets/builder.py", line 1739, in _prepare_split
                  for job_id, done, content in self._prepare_split_single(
                                               ^^^^^^^^^^^^^^^^^^^^^^^^^^^
                File "/usr/local/lib/python3.12/site-packages/datasets/builder.py", line 1922, in _prepare_split_single
                  raise DatasetGenerationError("An error occurred while generating the dataset") from e
              datasets.exceptions.DatasetGenerationError: An error occurred while generating the dataset

Need help to make the dataset viewer work? Make sure to review how to configure the dataset viewer, and open a discussion for direct support.

instruction
string
input
string
context
string
output
string
tags
list
source
string
confidence
float64
Classify this indexed RF audio item as likely operator traffic, calling-channel activity, or non-voice artifact.
filename=gqrx_20230410_154116_146520000.wav, callsign_label=KN6OS, sample_index=755
Use a monitoring and spectrum-logging viewpoint. Do not invent audio content that is not present in the metadata.
Most likely class: operator traffic or calling-channel voice activity. Reasoning: the label is `KN6OS`, the file name looks like a narrowband receive capture, and the context matches amateur simplex monitoring. Next step: check the clip for actual speech, unmodulated carriers, or noise signatures before adding it to a ...
[ "ham-radio", "classification", "audio-index", "monitoring" ]
daviddkarnowski/amateur-radio-transmissions-2-meter-fm-simplex
0.73
Assess this RF logging record and explain what an engineer should infer from it.
frequency_hz=160000000, frequency_mhz=160.000, signal_strength_dbm=-96.0, modulation=BPSK, bandwidth=10000, device_type=Halow-U, antenna_type=Omnidirectional, weather=Rainy, interference_type=Adjacent-channel, air_pressure=, device_status=Transmitting beacon signal, row_index=403
Focus on interpretation, signal quality, propagation context, and instrumentation limitations.
Signal assessment: 160.000 MHz sits in the VHF region and overlaps the general coverage amateur reference band when applicable. The measured level is -96.0 dBm, which is a weak receive level in many monitoring setups. The modulation is BPSK, the antenna is Omnidirectional, the device is Halow-U, and the reported interf...
[ "signals", "rf-logging", "bpsk", "measurement-interpretation" ]
suraj520/rf-signal-data
0.78
Predict the most useful next diagnostic checks for this RF measurement.
frequency_hz=160000000, frequency_mhz=160.000, signal_strength_dbm=-18.0, modulation=BPSK, bandwidth=200000, device_type=SteamDeck, antenna_type=Omnidirectional, weather=Rainy, interference_type=Intermodulation, air_pressure=, device_status=Running game, row_index=592
Answer like a methodical radio engineer reviewing logged metadata.
Recommended checks: 1) verify the receive chain and calibration for a -18.0 dBm reading, 2) confirm whether Intermodulation is consistent with nearby occupancy or a local artifact, 3) review whether the Omnidirectional antenna choice fits the target signal geometry, 4) compare this BPSK sample against neighboring captu...
[ "signals", "diagnostics", "bpsk", "rf-measurement" ]
suraj520/rf-signal-data
0.79
Turn this radio monitoring entry into a short training note for a new amateur operator.
recording=gqrx_20230609_153645_146520000.wav, label=KN6OS
Audience: beginner learning simplex monitoring habits.
Training note: a file labeled `KN6OS` from a 2-meter simplex monitor is useful for learning how stations appear in logs even before you review the audio. Listen first, identify whether the capture is real traffic or just noise labeling, and remember that calling frequencies are for making contact efficiently rather tha...
[ "ham-radio", "training", "simplex", "new-operator" ]
daviddkarnowski/amateur-radio-transmissions-2-meter-fm-simplex
0.75
Interpret this RF spectrum capture and explain whether it resembles normal occupancy or a possible interference event.
capture_file=2412mhz_jamming_9dbm_gaussiannoise_574.csv, capture_frequency_mhz=2412, derived_mean_rssi=14.7, derived_mean_relpwr_db=17.3, derived_mean_avgpwr_db=55.0, derived_mean_magnitude=52.1, class_hint=harmful interference candidate, emitter_hint=gaussian_noise, capture_index=195
Respond from a lawful monitoring and interference-analysis perspective only. Do not provide jamming instructions or offensive spectrum abuse guidance.
Spectrum interpretation: this sample looks like a harmful interference candidate. Mean RSSI is 14.7, relative power is 17.3 dB, average power is 55.0, and mean magnitude is 52.1 at approximately 2412 MHz. If elevated power persists across repeated captures, treat it as an interference investigation rather than a transm...
[ "signals", "interference-analysis", "spectrum-monitoring", "rf-diagnostics" ]
daniaherzalla/radio-frequency-jamming
0.79
Explain this RF log entry to a ham operator who wants band and equipment intuition.
frequency_hz=100000000, frequency_mhz=100.000, signal_strength_dbm=-75.0, modulation=BPSK, bandwidth=1000000, device_type=Halow-U, antenna_type=Yagi, weather=Sunny, interference_type=Intermodulation, air_pressure=, device_status=Transmitting beacon signal, row_index=939
Audience: operator learning how raw RF metadata maps to practical station thinking.
Practical read: 100.000 MHz places the sample in VHF and near the general coverage reference region when that mapping applies. A weak level with BPSK and 1000000 should be interpreted together, not alone. The Yagi antenna and Halow-U receiver may shape what was captured just as much as propagation does. Treat the inter...
[ "ham-radio", "signals", "band-intuition", "bpsk" ]
suraj520/rf-signal-data
0.77
Interpret this amateur radio recording index entry and explain what it suggests operationally.
filename=gqrx_20230331_155115_146520000.wav, callsign_label=KN6KNE
Assume the recordings are from the 2-meter simplex calling area. Focus on lawful amateur operation, observation, and signal classification.
Observation: this looks like amateur station activity. The filename suggests an observation near 146520000 Hz, which is consistent with 2-meter simplex activity when close to 146.520 MHz. If `KN6KNE` is a valid amateur callsign, likely use cases include calling, brief coordination, or local conversation rather than rep...
[ "ham-radio", "2m", "simplex", "signal-observation" ]
daviddkarnowski/amateur-radio-transmissions-2-meter-fm-simplex
0.74
Classify this indexed RF audio item as likely operator traffic, calling-channel activity, or non-voice artifact.
filename=gqrx_20230428_144713_146520000.wav, callsign_label=KE6ZGR, sample_index=415
Use a monitoring and spectrum-logging viewpoint. Do not invent audio content that is not present in the metadata.
Most likely class: operator traffic or calling-channel voice activity. Reasoning: the label is `KE6ZGR`, the file name looks like a narrowband receive capture, and the context matches amateur simplex monitoring. Next step: check the clip for actual speech, unmodulated carriers, or noise signatures before adding it to a...
[ "ham-radio", "classification", "audio-index", "monitoring" ]
daviddkarnowski/amateur-radio-transmissions-2-meter-fm-simplex
0.73
Classify this indexed RF audio item as likely operator traffic, calling-channel activity, or non-voice artifact.
filename=gqrx_20230505_033156_146520000.wav, callsign_label=KF6CNS, sample_index=747
Use a monitoring and spectrum-logging viewpoint. Do not invent audio content that is not present in the metadata.
Most likely class: operator traffic or calling-channel voice activity. Reasoning: the label is `KF6CNS`, the file name looks like a narrowband receive capture, and the context matches amateur simplex monitoring. Next step: check the clip for actual speech, unmodulated carriers, or noise signatures before adding it to a...
[ "ham-radio", "classification", "audio-index", "monitoring" ]
daviddkarnowski/amateur-radio-transmissions-2-meter-fm-simplex
0.73
Explain this RF log entry to a ham operator who wants band and equipment intuition.
frequency_hz=160000000, frequency_mhz=160.000, signal_strength_dbm=-99.0, modulation=AM, bandwidth=1000000, device_type=HackRF, antenna_type=Directional, weather=Sunny, interference_type=Intermodulation, air_pressure=, device_status=Streaming I/Q data, row_index=1110
Audience: operator learning how raw RF metadata maps to practical station thinking.
Practical read: 160.000 MHz places the sample in VHF and near the general coverage reference region when that mapping applies. A weak level with AM and 1000000 should be interpreted together, not alone. The Directional antenna and HackRF receiver may shape what was captured just as much as propagation does. Treat the i...
[ "ham-radio", "signals", "band-intuition", "am" ]
suraj520/rf-signal-data
0.77
Predict the most useful next diagnostic checks for this RF measurement.
frequency_hz=90000000, frequency_mhz=90.000, signal_strength_dbm=-63.0, modulation=BPSK, bandwidth=500000, device_type=HackRF, antenna_type=Yagi, weather=Rainy, interference_type=Adjacent-channel, air_pressure=, device_status=Streaming I/Q data, row_index=1117
Answer like a methodical radio engineer reviewing logged metadata.
Recommended checks: 1) verify the receive chain and calibration for a -63.0 dBm reading, 2) confirm whether Adjacent-channel is consistent with nearby occupancy or a local artifact, 3) review whether the Yagi antenna choice fits the target signal geometry, 4) compare this BPSK sample against neighboring captures on the...
[ "signals", "diagnostics", "bpsk", "rf-measurement" ]
suraj520/rf-signal-data
0.79
Turn this radio monitoring entry into a short training note for a new amateur operator.
recording=gqrx_20230327_142914_146520000.wav, label=KE6ZGR
Audience: beginner learning simplex monitoring habits.
Training note: a file labeled `KE6ZGR` from a 2-meter simplex monitor is useful for learning how stations appear in logs even before you review the audio. Listen first, identify whether the capture is real traffic or just noise labeling, and remember that calling frequencies are for making contact efficiently rather th...
[ "ham-radio", "training", "simplex", "new-operator" ]
daviddkarnowski/amateur-radio-transmissions-2-meter-fm-simplex
0.75
Turn this radio monitoring entry into a short training note for a new amateur operator.
recording=gqrx_20230326_070950_146520000.wav, label=N6EED
Audience: beginner learning simplex monitoring habits.
Training note: a file labeled `N6EED` from a 2-meter simplex monitor is useful for learning how stations appear in logs even before you review the audio. Listen first, identify whether the capture is real traffic or just noise labeling, and remember that calling frequencies are for making contact efficiently rather tha...
[ "ham-radio", "training", "simplex", "new-operator" ]
daviddkarnowski/amateur-radio-transmissions-2-meter-fm-simplex
0.75
Interpret this RF spectrum capture and explain whether it resembles normal occupancy or a possible interference event.
capture_file=5745mhz_jamming_9dbm_gaussiannoise_1584.csv, capture_frequency_mhz=5180, derived_mean_rssi=5.3, derived_mean_relpwr_db=9.3, derived_mean_avgpwr_db=57.1, derived_mean_magnitude=56.9, class_hint=harmful interference candidate, emitter_hint=gaussian_noise, capture_index=21
Respond from a lawful monitoring and interference-analysis perspective only. Do not provide jamming instructions or offensive spectrum abuse guidance.
Spectrum interpretation: this sample looks like a harmful interference candidate. Mean RSSI is 5.3, relative power is 9.3 dB, average power is 57.1, and mean magnitude is 56.9 at approximately 5180 MHz. If elevated power persists across repeated captures, treat it as an interference investigation rather than a transmis...
[ "signals", "interference-analysis", "spectrum-monitoring", "rf-diagnostics" ]
daniaherzalla/radio-frequency-jamming
0.79
Turn this radio monitoring entry into a short training note for a new amateur operator.
recording=gqrx_20230607_142230_146520000.wav, label=N6WOR
Audience: beginner learning simplex monitoring habits.
Training note: a file labeled `N6WOR` from a 2-meter simplex monitor is useful for learning how stations appear in logs even before you review the audio. Listen first, identify whether the capture is real traffic or just noise labeling, and remember that calling frequencies are for making contact efficiently rather tha...
[ "ham-radio", "training", "simplex", "new-operator" ]
daviddkarnowski/amateur-radio-transmissions-2-meter-fm-simplex
0.75
Assess this RF logging record and explain what an engineer should infer from it.
frequency_hz=100000000, frequency_mhz=100.000, signal_strength_dbm=-37.0, modulation=BPSK, bandwidth=200000, device_type=Halow-U, antenna_type=Omnidirectional, weather=Cloudy, interference_type=Intermodulation, air_pressure=, device_status=Transmitting beacon signal, row_index=138
Focus on interpretation, signal quality, propagation context, and instrumentation limitations.
Signal assessment: 100.000 MHz sits in the VHF region and overlaps the general coverage amateur reference band when applicable. The measured level is -37.0 dBm, which is a strong receive level in many monitoring setups. The modulation is BPSK, the antenna is Omnidirectional, the device is Halow-U, and the reported inte...
[ "signals", "rf-logging", "bpsk", "measurement-interpretation" ]
suraj520/rf-signal-data
0.78
Predict the most useful next diagnostic checks for this RF measurement.
frequency_hz=70000000, frequency_mhz=70.000, signal_strength_dbm=-77.0, modulation=BPSK, bandwidth=50000, device_type=HackRF, antenna_type=Omnidirectional, weather=Cloudy, interference_type=Co-channel, air_pressure=, device_status=Streaming I/Q data, row_index=1
Answer like a methodical radio engineer reviewing logged metadata.
Recommended checks: 1) verify the receive chain and calibration for a -77.0 dBm reading, 2) confirm whether Co-channel is consistent with nearby occupancy or a local artifact, 3) review whether the Omnidirectional antenna choice fits the target signal geometry, 4) compare this BPSK sample against neighboring captures o...
[ "signals", "diagnostics", "bpsk", "rf-measurement" ]
suraj520/rf-signal-data
0.79
Classify this indexed RF audio item as likely operator traffic, calling-channel activity, or non-voice artifact.
filename=gqrx_20230324_181826_146520000.wav, callsign_label=KN6OS, sample_index=211
Use a monitoring and spectrum-logging viewpoint. Do not invent audio content that is not present in the metadata.
Most likely class: operator traffic or calling-channel voice activity. Reasoning: the label is `KN6OS`, the file name looks like a narrowband receive capture, and the context matches amateur simplex monitoring. Next step: check the clip for actual speech, unmodulated carriers, or noise signatures before adding it to a ...
[ "ham-radio", "classification", "audio-index", "monitoring" ]
daviddkarnowski/amateur-radio-transmissions-2-meter-fm-simplex
0.73
Assess this RF logging record and explain what an engineer should infer from it.
frequency_hz=100000000, frequency_mhz=100.000, signal_strength_dbm=-4.0, modulation=8PSK, bandwidth=100000, device_type=Halow-U, antenna_type=Directional, weather=Cloudy, interference_type=None, air_pressure=, device_status=Transmitting beacon signal, row_index=475
Focus on interpretation, signal quality, propagation context, and instrumentation limitations.
Signal assessment: 100.000 MHz sits in the VHF region and overlaps the general coverage amateur reference band when applicable. The measured level is -4.0 dBm, which is a strong receive level in many monitoring setups. The modulation is 8PSK, the antenna is Directional, the device is Halow-U, and the reported interfere...
[ "signals", "rf-logging", "8psk", "measurement-interpretation" ]
suraj520/rf-signal-data
0.78
Classify this indexed RF audio item as likely operator traffic, calling-channel activity, or non-voice artifact.
filename=gqrx_20230505_015738_146520000.wav, callsign_label=KF6CNS, sample_index=769
Use a monitoring and spectrum-logging viewpoint. Do not invent audio content that is not present in the metadata.
Most likely class: operator traffic or calling-channel voice activity. Reasoning: the label is `KF6CNS`, the file name looks like a narrowband receive capture, and the context matches amateur simplex monitoring. Next step: check the clip for actual speech, unmodulated carriers, or noise signatures before adding it to a...
[ "ham-radio", "classification", "audio-index", "monitoring" ]
daviddkarnowski/amateur-radio-transmissions-2-meter-fm-simplex
0.73
Predict the most useful next diagnostic checks for this RF measurement.
frequency_hz=120000000, frequency_mhz=120.000, signal_strength_dbm=-88.0, modulation=8PSK, bandwidth=1000000, device_type=SteamDeck, antenna_type=Directional, weather=Cloudy, interference_type=Intermodulation, air_pressure=, device_status=Running game, row_index=892
Answer like a methodical radio engineer reviewing logged metadata.
Recommended checks: 1) verify the receive chain and calibration for a -88.0 dBm reading, 2) confirm whether Intermodulation is consistent with nearby occupancy or a local artifact, 3) review whether the Directional antenna choice fits the target signal geometry, 4) compare this 8PSK sample against neighboring captures ...
[ "signals", "diagnostics", "8psk", "rf-measurement" ]
suraj520/rf-signal-data
0.79
Explain this RF log entry to a ham operator who wants band and equipment intuition.
frequency_hz=140000000, frequency_mhz=140.000, signal_strength_dbm=-27.0, modulation=QAM, bandwidth=10000, device_type=Halow-U, antenna_type=Directional, weather=Cloudy, interference_type=Co-channel, air_pressure=, device_status=Transmitting beacon signal, row_index=399
Audience: operator learning how raw RF metadata maps to practical station thinking.
Practical read: 140.000 MHz places the sample in VHF and near the general coverage reference region when that mapping applies. A strong level with QAM and 10000 should be interpreted together, not alone. The Directional antenna and Halow-U receiver may shape what was captured just as much as propagation does. Treat the...
[ "ham-radio", "signals", "band-intuition", "qam" ]
suraj520/rf-signal-data
0.77
Predict the most useful next diagnostic checks for this RF measurement.
frequency_hz=70000000, frequency_mhz=70.000, signal_strength_dbm=-77.0, modulation=QPSK, bandwidth=1000000, device_type=Halow-U, antenna_type=Directional, weather=Rainy, interference_type=None, air_pressure=, device_status=Transmitting beacon signal, row_index=386
Answer like a methodical radio engineer reviewing logged metadata.
Recommended checks: 1) verify the receive chain and calibration for a -77.0 dBm reading, 2) confirm whether None is consistent with nearby occupancy or a local artifact, 3) review whether the Directional antenna choice fits the target signal geometry, 4) compare this QPSK sample against neighboring captures on the same...
[ "signals", "diagnostics", "qpsk", "rf-measurement" ]
suraj520/rf-signal-data
0.79
Interpret this amateur radio recording index entry and explain what it suggests operationally.
filename=gqrx_20230523_221656_146520000.wav, callsign_label=WA6LDI
Assume the recordings are from the 2-meter simplex calling area. Focus on lawful amateur operation, observation, and signal classification.
Observation: this looks like amateur station activity. The filename suggests an observation near 146520000 Hz, which is consistent with 2-meter simplex activity when close to 146.520 MHz. If `WA6LDI` is a valid amateur callsign, likely use cases include calling, brief coordination, or local conversation rather than rep...
[ "ham-radio", "2m", "simplex", "signal-observation" ]
daviddkarnowski/amateur-radio-transmissions-2-meter-fm-simplex
0.74
Assess this RF logging record and explain what an engineer should infer from it.
frequency_hz=70000000, frequency_mhz=70.000, signal_strength_dbm=-69.0, modulation=BPSK, bandwidth=500000, device_type=HackRF, antenna_type=Yagi, weather=Cloudy, interference_type=None, air_pressure=, device_status=Streaming I/Q data, row_index=392
Focus on interpretation, signal quality, propagation context, and instrumentation limitations.
Signal assessment: 70.000 MHz sits in the VHF region and overlaps the general coverage amateur reference band when applicable. The measured level is -69.0 dBm, which is a moderate receive level in many monitoring setups. The modulation is BPSK, the antenna is Yagi, the device is HackRF, and the reported interference mo...
[ "signals", "rf-logging", "bpsk", "measurement-interpretation" ]
suraj520/rf-signal-data
0.78
Predict the most useful next diagnostic checks for this RF measurement.
frequency_hz=70000000, frequency_mhz=70.000, signal_strength_dbm=-56.0, modulation=BPSK, bandwidth=100000, device_type=SteamDeck, antenna_type=Dipole, weather=Cloudy, interference_type=Adjacent-channel, air_pressure=, device_status=Running game, row_index=1114
Answer like a methodical radio engineer reviewing logged metadata.
Recommended checks: 1) verify the receive chain and calibration for a -56.0 dBm reading, 2) confirm whether Adjacent-channel is consistent with nearby occupancy or a local artifact, 3) review whether the Dipole antenna choice fits the target signal geometry, 4) compare this BPSK sample against neighboring captures on t...
[ "signals", "diagnostics", "bpsk", "rf-measurement" ]
suraj520/rf-signal-data
0.79
Classify this indexed RF audio item as likely operator traffic, calling-channel activity, or non-voice artifact.
filename=gqrx_20230322_224651_146520000.wav, callsign_label=W6MDE, sample_index=1099
Use a monitoring and spectrum-logging viewpoint. Do not invent audio content that is not present in the metadata.
Most likely class: operator traffic or calling-channel voice activity. Reasoning: the label is `W6MDE`, the file name looks like a narrowband receive capture, and the context matches amateur simplex monitoring. Next step: check the clip for actual speech, unmodulated carriers, or noise signatures before adding it to a ...
[ "ham-radio", "classification", "audio-index", "monitoring" ]
daviddkarnowski/amateur-radio-transmissions-2-meter-fm-simplex
0.73
Explain this RF log entry to a ham operator who wants band and equipment intuition.
frequency_hz=70000000, frequency_mhz=70.000, signal_strength_dbm=-61.0, modulation=AM, bandwidth=200000, device_type=SteamDeck, antenna_type=Dipole, weather=Sunny, interference_type=None, air_pressure=, device_status=Running game, row_index=1098
Audience: operator learning how raw RF metadata maps to practical station thinking.
Practical read: 70.000 MHz places the sample in VHF and near the general coverage reference region when that mapping applies. A moderate level with AM and 200000 should be interpreted together, not alone. The Dipole antenna and SteamDeck receiver may shape what was captured just as much as propagation does. Treat the i...
[ "ham-radio", "signals", "band-intuition", "am" ]
suraj520/rf-signal-data
0.77
Interpret this amateur radio recording index entry and explain what it suggests operationally.
filename=gqrx_20230327_021640_146520000.wav, callsign_label=W6TON
Assume the recordings are from the 2-meter simplex calling area. Focus on lawful amateur operation, observation, and signal classification.
Observation: this looks like amateur station activity. The filename suggests an observation near 146520000 Hz, which is consistent with 2-meter simplex activity when close to 146.520 MHz. If `W6TON` is a valid amateur callsign, likely use cases include calling, brief coordination, or local conversation rather than repe...
[ "ham-radio", "2m", "simplex", "signal-observation" ]
daviddkarnowski/amateur-radio-transmissions-2-meter-fm-simplex
0.74
Assess this RF logging record and explain what an engineer should infer from it.
frequency_hz=90000000, frequency_mhz=90.000, signal_strength_dbm=-77.0, modulation=BPSK, bandwidth=200000, device_type=HackRF, antenna_type=Omnidirectional, weather=Rainy, interference_type=None, air_pressure=, device_status=Streaming I/Q data, row_index=234
Focus on interpretation, signal quality, propagation context, and instrumentation limitations.
Signal assessment: 90.000 MHz sits in the VHF region and overlaps the general coverage amateur reference band when applicable. The measured level is -77.0 dBm, which is a weak receive level in many monitoring setups. The modulation is BPSK, the antenna is Omnidirectional, the device is HackRF, and the reported interfer...
[ "signals", "rf-logging", "bpsk", "measurement-interpretation" ]
suraj520/rf-signal-data
0.78
Interpret this amateur radio recording index entry and explain what it suggests operationally.
filename=gqrx_20230413_232142_146520000.wav, callsign_label=N6WOR
Assume the recordings are from the 2-meter simplex calling area. Focus on lawful amateur operation, observation, and signal classification.
Observation: this looks like amateur station activity. The filename suggests an observation near 146520000 Hz, which is consistent with 2-meter simplex activity when close to 146.520 MHz. If `N6WOR` is a valid amateur callsign, likely use cases include calling, brief coordination, or local conversation rather than repe...
[ "ham-radio", "2m", "simplex", "signal-observation" ]
daviddkarnowski/amateur-radio-transmissions-2-meter-fm-simplex
0.74
Classify this indexed RF audio item as likely operator traffic, calling-channel activity, or non-voice artifact.
filename=gqrx_20230506_184943_146520000.wav, callsign_label=KI6PMD, sample_index=487
Use a monitoring and spectrum-logging viewpoint. Do not invent audio content that is not present in the metadata.
Most likely class: operator traffic or calling-channel voice activity. Reasoning: the label is `KI6PMD`, the file name looks like a narrowband receive capture, and the context matches amateur simplex monitoring. Next step: check the clip for actual speech, unmodulated carriers, or noise signatures before adding it to a...
[ "ham-radio", "classification", "audio-index", "monitoring" ]
daviddkarnowski/amateur-radio-transmissions-2-meter-fm-simplex
0.73
Turn this radio monitoring entry into a short training note for a new amateur operator.
recording=gqrx_20230504_143419_146520000.wav, label=N6YYO
Audience: beginner learning simplex monitoring habits.
Training note: a file labeled `N6YYO` from a 2-meter simplex monitor is useful for learning how stations appear in logs even before you review the audio. Listen first, identify whether the capture is real traffic or just noise labeling, and remember that calling frequencies are for making contact efficiently rather tha...
[ "ham-radio", "training", "simplex", "new-operator" ]
daviddkarnowski/amateur-radio-transmissions-2-meter-fm-simplex
0.75
Assess this RF logging record and explain what an engineer should infer from it.
frequency_hz=140000000, frequency_mhz=140.000, signal_strength_dbm=-61.0, modulation=AM, bandwidth=100000, device_type=Halow-U, antenna_type=Directional, weather=Sunny, interference_type=Adjacent-channel, air_pressure=, device_status=Transmitting beacon signal, row_index=822
Focus on interpretation, signal quality, propagation context, and instrumentation limitations.
Signal assessment: 140.000 MHz sits in the VHF region and overlaps the general coverage amateur reference band when applicable. The measured level is -61.0 dBm, which is a moderate receive level in many monitoring setups. The modulation is AM, the antenna is Directional, the device is Halow-U, and the reported interfer...
[ "signals", "rf-logging", "am", "measurement-interpretation" ]
suraj520/rf-signal-data
0.78
Predict the most useful next diagnostic checks for this RF measurement.
frequency_hz=100000000, frequency_mhz=100.000, signal_strength_dbm=-16.0, modulation=8PSK, bandwidth=10000, device_type=SteamDeck, antenna_type=Directional, weather=Sunny, interference_type=Co-channel, air_pressure=, device_status=Running game, row_index=247
Answer like a methodical radio engineer reviewing logged metadata.
Recommended checks: 1) verify the receive chain and calibration for a -16.0 dBm reading, 2) confirm whether Co-channel is consistent with nearby occupancy or a local artifact, 3) review whether the Directional antenna choice fits the target signal geometry, 4) compare this 8PSK sample against neighboring captures on th...
[ "signals", "diagnostics", "8psk", "rf-measurement" ]
suraj520/rf-signal-data
0.79
Assess this RF logging record and explain what an engineer should infer from it.
frequency_hz=70000000, frequency_mhz=70.000, signal_strength_dbm=-79.0, modulation=QPSK, bandwidth=500000, device_type=SteamDeck, antenna_type=Omnidirectional, weather=Rainy, interference_type=Co-channel, air_pressure=, device_status=Running game, row_index=726
Focus on interpretation, signal quality, propagation context, and instrumentation limitations.
Signal assessment: 70.000 MHz sits in the VHF region and overlaps the general coverage amateur reference band when applicable. The measured level is -79.0 dBm, which is a weak receive level in many monitoring setups. The modulation is QPSK, the antenna is Omnidirectional, the device is SteamDeck, and the reported inter...
[ "signals", "rf-logging", "qpsk", "measurement-interpretation" ]
suraj520/rf-signal-data
0.78
Explain this RF log entry to a ham operator who wants band and equipment intuition.
frequency_hz=100000000, frequency_mhz=100.000, signal_strength_dbm=-20.0, modulation=8PSK, bandwidth=1000000, device_type=Halow-U, antenna_type=Yagi, weather=Sunny, interference_type=Co-channel, air_pressure=, device_status=Transmitting beacon signal, row_index=659
Audience: operator learning how raw RF metadata maps to practical station thinking.
Practical read: 100.000 MHz places the sample in VHF and near the general coverage reference region when that mapping applies. A strong level with 8PSK and 1000000 should be interpreted together, not alone. The Yagi antenna and Halow-U receiver may shape what was captured just as much as propagation does. Treat the int...
[ "ham-radio", "signals", "band-intuition", "8psk" ]
suraj520/rf-signal-data
0.77
Explain this RF log entry to a ham operator who wants band and equipment intuition.
frequency_hz=160000000, frequency_mhz=160.000, signal_strength_dbm=-68.0, modulation=8PSK, bandwidth=200000, device_type=SteamDeck, antenna_type=Omnidirectional, weather=Sunny, interference_type=Co-channel, air_pressure=, device_status=Running game, row_index=906
Audience: operator learning how raw RF metadata maps to practical station thinking.
Practical read: 160.000 MHz places the sample in VHF and near the general coverage reference region when that mapping applies. A moderate level with 8PSK and 200000 should be interpreted together, not alone. The Omnidirectional antenna and SteamDeck receiver may shape what was captured just as much as propagation does....
[ "ham-radio", "signals", "band-intuition", "8psk" ]
suraj520/rf-signal-data
0.77
Turn this radio monitoring entry into a short training note for a new amateur operator.
recording=gqrx_20230610_181158_146520000.wav, label=N6KN
Audience: beginner learning simplex monitoring habits.
Training note: a file labeled `N6KN` from a 2-meter simplex monitor is useful for learning how stations appear in logs even before you review the audio. Listen first, identify whether the capture is real traffic or just noise labeling, and remember that calling frequencies are for making contact efficiently rather than...
[ "ham-radio", "training", "simplex", "new-operator" ]
daviddkarnowski/amateur-radio-transmissions-2-meter-fm-simplex
0.75
Convert this spectrum-monitoring sample into a safe incident-note style summary.
capture_file=5805mhz_jamming_neg10dbm_singletone_78.csv, capture_frequency_mhz=5805, derived_mean_rssi=12.3, derived_mean_relpwr_db=9.7, derived_mean_avgpwr_db=55.6, derived_mean_magnitude=164.6, class_hint=harmful interference candidate, emitter_hint=singletone, capture_index=14
Write as if the reader is documenting observations for later technical review.
Incident-note summary: capture `5805mhz_jamming_neg10dbm_singletone_78.csv` shows a harmful interference candidate profile near 5805 MHz with mean RSSI 12.3. The emitter hint `singletone` should be treated as a classification clue, not final proof. Recommended note fields are time, location, receiver setup, repeated-ob...
[ "signals", "incident-note", "spectrum-monitoring", "safe-analysis" ]
daniaherzalla/radio-frequency-jamming
0.8
Interpret this amateur radio recording index entry and explain what it suggests operationally.
filename=gqrx_20230503_185550_146520000.wav, callsign_label=KN6OS
Assume the recordings are from the 2-meter simplex calling area. Focus on lawful amateur operation, observation, and signal classification.
Observation: this looks like amateur station activity. The filename suggests an observation near 146520000 Hz, which is consistent with 2-meter simplex activity when close to 146.520 MHz. If `KN6OS` is a valid amateur callsign, likely use cases include calling, brief coordination, or local conversation rather than repe...
[ "ham-radio", "2m", "simplex", "signal-observation" ]
daviddkarnowski/amateur-radio-transmissions-2-meter-fm-simplex
0.74
Turn this radio monitoring entry into a short training note for a new amateur operator.
recording=gqrx_20230401_164902_146520000.wav, label=KN6OS
Audience: beginner learning simplex monitoring habits.
Training note: a file labeled `KN6OS` from a 2-meter simplex monitor is useful for learning how stations appear in logs even before you review the audio. Listen first, identify whether the capture is real traffic or just noise labeling, and remember that calling frequencies are for making contact efficiently rather tha...
[ "ham-radio", "training", "simplex", "new-operator" ]
daviddkarnowski/amateur-radio-transmissions-2-meter-fm-simplex
0.75
Predict the most useful next diagnostic checks for this RF measurement.
frequency_hz=140000000, frequency_mhz=140.000, signal_strength_dbm=-12.0, modulation=AM, bandwidth=200000, device_type=Halow-U, antenna_type=Yagi, weather=Rainy, interference_type=Adjacent-channel, air_pressure=, device_status=Transmitting beacon signal, row_index=505
Answer like a methodical radio engineer reviewing logged metadata.
Recommended checks: 1) verify the receive chain and calibration for a -12.0 dBm reading, 2) confirm whether Adjacent-channel is consistent with nearby occupancy or a local artifact, 3) review whether the Yagi antenna choice fits the target signal geometry, 4) compare this AM sample against neighboring captures on the s...
[ "signals", "diagnostics", "am", "rf-measurement" ]
suraj520/rf-signal-data
0.79
Predict the most useful next diagnostic checks for this RF measurement.
frequency_hz=160000000, frequency_mhz=160.000, signal_strength_dbm=-69.0, modulation=8PSK, bandwidth=200000, device_type=Halow-U, antenna_type=Omnidirectional, weather=Rainy, interference_type=None, air_pressure=, device_status=Transmitting beacon signal, row_index=802
Answer like a methodical radio engineer reviewing logged metadata.
Recommended checks: 1) verify the receive chain and calibration for a -69.0 dBm reading, 2) confirm whether None is consistent with nearby occupancy or a local artifact, 3) review whether the Omnidirectional antenna choice fits the target signal geometry, 4) compare this 8PSK sample against neighboring captures on the ...
[ "signals", "diagnostics", "8psk", "rf-measurement" ]
suraj520/rf-signal-data
0.79
Convert this spectrum-monitoring sample into a safe incident-note style summary.
capture_file=2457mhz_jamming_3dbm_gaussiannoise_316.csv, capture_frequency_mhz=2412, derived_mean_rssi=14.6, derived_mean_relpwr_db=14.8, derived_mean_avgpwr_db=52.2, derived_mean_magnitude=40.4, class_hint=harmful interference candidate, emitter_hint=gaussian_noise, capture_index=183
Write as if the reader is documenting observations for later technical review.
Incident-note summary: capture `2457mhz_jamming_3dbm_gaussiannoise_316.csv` shows a harmful interference candidate profile near 2412 MHz with mean RSSI 14.6. The emitter hint `gaussian_noise` should be treated as a classification clue, not final proof. Recommended note fields are time, location, receiver setup, repeate...
[ "signals", "incident-note", "spectrum-monitoring", "safe-analysis" ]
daniaherzalla/radio-frequency-jamming
0.8
Interpret this amateur radio recording index entry and explain what it suggests operationally.
filename=gqrx_20230608_115705_146520000.wav, callsign_label=KN6OS
Assume the recordings are from the 2-meter simplex calling area. Focus on lawful amateur operation, observation, and signal classification.
Observation: this looks like amateur station activity. The filename suggests an observation near 146520000 Hz, which is consistent with 2-meter simplex activity when close to 146.520 MHz. If `KN6OS` is a valid amateur callsign, likely use cases include calling, brief coordination, or local conversation rather than repe...
[ "ham-radio", "2m", "simplex", "signal-observation" ]
daviddkarnowski/amateur-radio-transmissions-2-meter-fm-simplex
0.74
Predict the most useful next diagnostic checks for this RF measurement.
frequency_hz=140000000, frequency_mhz=140.000, signal_strength_dbm=-92.0, modulation=AM, bandwidth=500000, device_type=Halow-U, antenna_type=Yagi, weather=Cloudy, interference_type=Intermodulation, air_pressure=, device_status=Transmitting beacon signal, row_index=450
Answer like a methodical radio engineer reviewing logged metadata.
Recommended checks: 1) verify the receive chain and calibration for a -92.0 dBm reading, 2) confirm whether Intermodulation is consistent with nearby occupancy or a local artifact, 3) review whether the Yagi antenna choice fits the target signal geometry, 4) compare this AM sample against neighboring captures on the sa...
[ "signals", "diagnostics", "am", "rf-measurement" ]
suraj520/rf-signal-data
0.79
Predict the most useful next diagnostic checks for this RF measurement.
frequency_hz=160000000, frequency_mhz=160.000, signal_strength_dbm=-54.0, modulation=QPSK, bandwidth=100000, device_type=HackRF, antenna_type=Directional, weather=Rainy, interference_type=Intermodulation, air_pressure=, device_status=Streaming I/Q data, row_index=343
Answer like a methodical radio engineer reviewing logged metadata.
Recommended checks: 1) verify the receive chain and calibration for a -54.0 dBm reading, 2) confirm whether Intermodulation is consistent with nearby occupancy or a local artifact, 3) review whether the Directional antenna choice fits the target signal geometry, 4) compare this QPSK sample against neighboring captures ...
[ "signals", "diagnostics", "qpsk", "rf-measurement" ]
suraj520/rf-signal-data
0.79
Interpret this amateur radio recording index entry and explain what it suggests operationally.
filename=gqrx_20230324_152123_146520000.wav, callsign_label=KE6ZGR
Assume the recordings are from the 2-meter simplex calling area. Focus on lawful amateur operation, observation, and signal classification.
Observation: this looks like amateur station activity. The filename suggests an observation near 146520000 Hz, which is consistent with 2-meter simplex activity when close to 146.520 MHz. If `KE6ZGR` is a valid amateur callsign, likely use cases include calling, brief coordination, or local conversation rather than rep...
[ "ham-radio", "2m", "simplex", "signal-observation" ]
daviddkarnowski/amateur-radio-transmissions-2-meter-fm-simplex
0.74
Turn this radio monitoring entry into a short training note for a new amateur operator.
recording=gqrx_20230324_182009_146520000.wav, label=KN6OS
Audience: beginner learning simplex monitoring habits.
Training note: a file labeled `KN6OS` from a 2-meter simplex monitor is useful for learning how stations appear in logs even before you review the audio. Listen first, identify whether the capture is real traffic or just noise labeling, and remember that calling frequencies are for making contact efficiently rather tha...
[ "ham-radio", "training", "simplex", "new-operator" ]
daviddkarnowski/amateur-radio-transmissions-2-meter-fm-simplex
0.75
Convert this spectrum-monitoring sample into a safe incident-note style summary.
capture_file=5ghz_passivescan_background_loc1_13083.csv, capture_frequency_mhz=5180, derived_mean_rssi=5.3, derived_mean_relpwr_db=9.0, derived_mean_avgpwr_db=57.8, derived_mean_magnitude=52.9, class_hint=benign baseline, emitter_hint=background, capture_index=178
Write as if the reader is documenting observations for later technical review.
Incident-note summary: capture `5ghz_passivescan_background_loc1_13083.csv` shows a benign baseline profile near 5180 MHz with mean RSSI 5.3. The emitter hint `background` should be treated as a classification clue, not final proof. Recommended note fields are time, location, receiver setup, repeated-observation status...
[ "signals", "incident-note", "spectrum-monitoring", "safe-analysis" ]
daniaherzalla/radio-frequency-jamming
0.8
Predict the most useful next diagnostic checks for this RF measurement.
frequency_hz=100000000, frequency_mhz=100.000, signal_strength_dbm=-55.0, modulation=FM, bandwidth=50000, device_type=SteamDeck, antenna_type=Dipole, weather=Cloudy, interference_type=Co-channel, air_pressure=, device_status=Running game, row_index=440
Answer like a methodical radio engineer reviewing logged metadata.
Recommended checks: 1) verify the receive chain and calibration for a -55.0 dBm reading, 2) confirm whether Co-channel is consistent with nearby occupancy or a local artifact, 3) review whether the Dipole antenna choice fits the target signal geometry, 4) compare this FM sample against neighboring captures on the same ...
[ "signals", "diagnostics", "fm", "rf-measurement" ]
suraj520/rf-signal-data
0.79
Convert this spectrum-monitoring sample into a safe incident-note style summary.
capture_file=2.4ghz_passivescan_background_loc2_3949.csv, capture_frequency_mhz=2412, derived_mean_rssi=14.2, derived_mean_relpwr_db=12.7, derived_mean_avgpwr_db=55.2, derived_mean_magnitude=79.9, class_hint=benign baseline, emitter_hint=background, capture_index=40
Write as if the reader is documenting observations for later technical review.
Incident-note summary: capture `2.4ghz_passivescan_background_loc2_3949.csv` shows a benign baseline profile near 2412 MHz with mean RSSI 14.2. The emitter hint `background` should be treated as a classification clue, not final proof. Recommended note fields are time, location, receiver setup, repeated-observation stat...
[ "signals", "incident-note", "spectrum-monitoring", "safe-analysis" ]
daniaherzalla/radio-frequency-jamming
0.8
Classify this indexed RF audio item as likely operator traffic, calling-channel activity, or non-voice artifact.
filename=gqrx_20230609_234428_146520000.wav, callsign_label=KE6ZGR, sample_index=18
Use a monitoring and spectrum-logging viewpoint. Do not invent audio content that is not present in the metadata.
Most likely class: operator traffic or calling-channel voice activity. Reasoning: the label is `KE6ZGR`, the file name looks like a narrowband receive capture, and the context matches amateur simplex monitoring. Next step: check the clip for actual speech, unmodulated carriers, or noise signatures before adding it to a...
[ "ham-radio", "classification", "audio-index", "monitoring" ]
daviddkarnowski/amateur-radio-transmissions-2-meter-fm-simplex
0.73
Turn this radio monitoring entry into a short training note for a new amateur operator.
recording=gqrx_20230330_025626_146520000.wav, label=KA6JMM
Audience: beginner learning simplex monitoring habits.
Training note: a file labeled `KA6JMM` from a 2-meter simplex monitor is useful for learning how stations appear in logs even before you review the audio. Listen first, identify whether the capture is real traffic or just noise labeling, and remember that calling frequencies are for making contact efficiently rather th...
[ "ham-radio", "training", "simplex", "new-operator" ]
daviddkarnowski/amateur-radio-transmissions-2-meter-fm-simplex
0.75
Classify this indexed RF audio item as likely operator traffic, calling-channel activity, or non-voice artifact.
filename=gqrx_20230506_205123_146520000.wav, callsign_label=STATIC, sample_index=120
Use a monitoring and spectrum-logging viewpoint. Do not invent audio content that is not present in the metadata.
Most likely class: non-voice artifact or noise marker. Reasoning: the label is `STATIC`, the file name looks like a narrowband receive capture, and the context matches amateur simplex monitoring. Next step: check the clip for actual speech, unmodulated carriers, or noise signatures before adding it to a station log.
[ "ham-radio", "classification", "audio-index", "monitoring" ]
daviddkarnowski/amateur-radio-transmissions-2-meter-fm-simplex
0.73
Interpret this amateur radio recording index entry and explain what it suggests operationally.
filename=gqrx_20230427_145901_146520000.wav, callsign_label=KN6OS
Assume the recordings are from the 2-meter simplex calling area. Focus on lawful amateur operation, observation, and signal classification.
Observation: this looks like amateur station activity. The filename suggests an observation near 146520000 Hz, which is consistent with 2-meter simplex activity when close to 146.520 MHz. If `KN6OS` is a valid amateur callsign, likely use cases include calling, brief coordination, or local conversation rather than repe...
[ "ham-radio", "2m", "simplex", "signal-observation" ]
daviddkarnowski/amateur-radio-transmissions-2-meter-fm-simplex
0.74
Classify this indexed RF audio item as likely operator traffic, calling-channel activity, or non-voice artifact.
filename=gqrx_20230320_154058_146520000.wav, callsign_label=KE6ZGR, sample_index=1064
Use a monitoring and spectrum-logging viewpoint. Do not invent audio content that is not present in the metadata.
Most likely class: operator traffic or calling-channel voice activity. Reasoning: the label is `KE6ZGR`, the file name looks like a narrowband receive capture, and the context matches amateur simplex monitoring. Next step: check the clip for actual speech, unmodulated carriers, or noise signatures before adding it to a...
[ "ham-radio", "classification", "audio-index", "monitoring" ]
daviddkarnowski/amateur-radio-transmissions-2-meter-fm-simplex
0.73
Explain this RF log entry to a ham operator who wants band and equipment intuition.
frequency_hz=90000000, frequency_mhz=90.000, signal_strength_dbm=-74.0, modulation=FM, bandwidth=200000, device_type=HackRF, antenna_type=Dipole, weather=Sunny, interference_type=None, air_pressure=, device_status=Streaming I/Q data, row_index=644
Audience: operator learning how raw RF metadata maps to practical station thinking.
Practical read: 90.000 MHz places the sample in VHF and near the general coverage reference region when that mapping applies. A weak level with FM and 200000 should be interpreted together, not alone. The Dipole antenna and HackRF receiver may shape what was captured just as much as propagation does. Treat the interfer...
[ "ham-radio", "signals", "band-intuition", "fm" ]
suraj520/rf-signal-data
0.77
Predict the most useful next diagnostic checks for this RF measurement.
frequency_hz=100000000, frequency_mhz=100.000, signal_strength_dbm=-15.0, modulation=AM, bandwidth=10000, device_type=Halow-U, antenna_type=Directional, weather=Rainy, interference_type=Adjacent-channel, air_pressure=, device_status=Transmitting beacon signal, row_index=945
Answer like a methodical radio engineer reviewing logged metadata.
Recommended checks: 1) verify the receive chain and calibration for a -15.0 dBm reading, 2) confirm whether Adjacent-channel is consistent with nearby occupancy or a local artifact, 3) review whether the Directional antenna choice fits the target signal geometry, 4) compare this AM sample against neighboring captures o...
[ "signals", "diagnostics", "am", "rf-measurement" ]
suraj520/rf-signal-data
0.79
Explain this RF log entry to a ham operator who wants band and equipment intuition.
frequency_hz=120000000, frequency_mhz=120.000, signal_strength_dbm=-54.0, modulation=8PSK, bandwidth=50000, device_type=SteamDeck, antenna_type=Omnidirectional, weather=Rainy, interference_type=Adjacent-channel, air_pressure=, device_status=Running game, row_index=1149
Audience: operator learning how raw RF metadata maps to practical station thinking.
Practical read: 120.000 MHz places the sample in VHF and near the general coverage reference region when that mapping applies. A moderate level with 8PSK and 50000 should be interpreted together, not alone. The Omnidirectional antenna and SteamDeck receiver may shape what was captured just as much as propagation does. ...
[ "ham-radio", "signals", "band-intuition", "8psk" ]
suraj520/rf-signal-data
0.77
Convert this spectrum-monitoring sample into a safe incident-note style summary.
capture_file=5ghz_passivescan_background_loc2_2110.csv, capture_frequency_mhz=5180, derived_mean_rssi=9.0, derived_mean_relpwr_db=9.7, derived_mean_avgpwr_db=58.0, derived_mean_magnitude=44.0, class_hint=benign baseline, emitter_hint=background, capture_index=149
Write as if the reader is documenting observations for later technical review.
Incident-note summary: capture `5ghz_passivescan_background_loc2_2110.csv` shows a benign baseline profile near 5180 MHz with mean RSSI 9.0. The emitter hint `background` should be treated as a classification clue, not final proof. Recommended note fields are time, location, receiver setup, repeated-observation status,...
[ "signals", "incident-note", "spectrum-monitoring", "safe-analysis" ]
daniaherzalla/radio-frequency-jamming
0.8
Explain this RF log entry to a ham operator who wants band and equipment intuition.
frequency_hz=90000000, frequency_mhz=90.000, signal_strength_dbm=0.0, modulation=QPSK, bandwidth=500000, device_type=SteamDeck, antenna_type=Omnidirectional, weather=Rainy, interference_type=Co-channel, air_pressure=, device_status=Running game, row_index=182
Audience: operator learning how raw RF metadata maps to practical station thinking.
Practical read: 90.000 MHz places the sample in VHF and near the general coverage reference region when that mapping applies. A strong level with QPSK and 500000 should be interpreted together, not alone. The Omnidirectional antenna and SteamDeck receiver may shape what was captured just as much as propagation does. Tr...
[ "ham-radio", "signals", "band-intuition", "qpsk" ]
suraj520/rf-signal-data
0.77
Explain this RF log entry to a ham operator who wants band and equipment intuition.
frequency_hz=100000000, frequency_mhz=100.000, signal_strength_dbm=-16.0, modulation=8PSK, bandwidth=10000, device_type=SteamDeck, antenna_type=Directional, weather=Sunny, interference_type=Co-channel, air_pressure=, device_status=Running game, row_index=247
Audience: operator learning how raw RF metadata maps to practical station thinking.
Practical read: 100.000 MHz places the sample in VHF and near the general coverage reference region when that mapping applies. A strong level with 8PSK and 10000 should be interpreted together, not alone. The Directional antenna and SteamDeck receiver may shape what was captured just as much as propagation does. Treat ...
[ "ham-radio", "signals", "band-intuition", "8psk" ]
suraj520/rf-signal-data
0.77
Convert this spectrum-monitoring sample into a safe incident-note style summary.
capture_file=2457mhz_jamming_12dbm_gaussiannoise_716.csv, capture_frequency_mhz=2412, derived_mean_rssi=22.1, derived_mean_relpwr_db=12.8, derived_mean_avgpwr_db=55.5, derived_mean_magnitude=51.0, class_hint=harmful interference candidate, emitter_hint=gaussian_noise, capture_index=117
Write as if the reader is documenting observations for later technical review.
Incident-note summary: capture `2457mhz_jamming_12dbm_gaussiannoise_716.csv` shows a harmful interference candidate profile near 2412 MHz with mean RSSI 22.1. The emitter hint `gaussian_noise` should be treated as a classification clue, not final proof. Recommended note fields are time, location, receiver setup, repeat...
[ "signals", "incident-note", "spectrum-monitoring", "safe-analysis" ]
daniaherzalla/radio-frequency-jamming
0.8
Turn this radio monitoring entry into a short training note for a new amateur operator.
recording=gqrx_20230429_163744_146520000.wav, label=KN6NJP
Audience: beginner learning simplex monitoring habits.
Training note: a file labeled `KN6NJP` from a 2-meter simplex monitor is useful for learning how stations appear in logs even before you review the audio. Listen first, identify whether the capture is real traffic or just noise labeling, and remember that calling frequencies are for making contact efficiently rather th...
[ "ham-radio", "training", "simplex", "new-operator" ]
daviddkarnowski/amateur-radio-transmissions-2-meter-fm-simplex
0.75
Classify this indexed RF audio item as likely operator traffic, calling-channel activity, or non-voice artifact.
filename=gqrx_20230610_202512_146520000.wav, callsign_label=N6KN, sample_index=1081
Use a monitoring and spectrum-logging viewpoint. Do not invent audio content that is not present in the metadata.
Most likely class: operator traffic or calling-channel voice activity. Reasoning: the label is `N6KN`, the file name looks like a narrowband receive capture, and the context matches amateur simplex monitoring. Next step: check the clip for actual speech, unmodulated carriers, or noise signatures before adding it to a s...
[ "ham-radio", "classification", "audio-index", "monitoring" ]
daviddkarnowski/amateur-radio-transmissions-2-meter-fm-simplex
0.73
Explain this RF log entry to a ham operator who wants band and equipment intuition.
frequency_hz=70000000, frequency_mhz=70.000, signal_strength_dbm=-88.0, modulation=FM, bandwidth=100000, device_type=Halow-U, antenna_type=Directional, weather=Rainy, interference_type=Co-channel, air_pressure=, device_status=Transmitting beacon signal, row_index=1196
Audience: operator learning how raw RF metadata maps to practical station thinking.
Practical read: 70.000 MHz places the sample in VHF and near the general coverage reference region when that mapping applies. A weak level with FM and 100000 should be interpreted together, not alone. The Directional antenna and Halow-U receiver may shape what was captured just as much as propagation does. Treat the in...
[ "ham-radio", "signals", "band-intuition", "fm" ]
suraj520/rf-signal-data
0.77
Explain this RF log entry to a ham operator who wants band and equipment intuition.
frequency_hz=100000000, frequency_mhz=100.000, signal_strength_dbm=-61.0, modulation=FM, bandwidth=100000, device_type=SteamDeck, antenna_type=Directional, weather=Cloudy, interference_type=None, air_pressure=, device_status=Running game, row_index=50
Audience: operator learning how raw RF metadata maps to practical station thinking.
Practical read: 100.000 MHz places the sample in VHF and near the general coverage reference region when that mapping applies. A moderate level with FM and 100000 should be interpreted together, not alone. The Directional antenna and SteamDeck receiver may shape what was captured just as much as propagation does. Treat...
[ "ham-radio", "signals", "band-intuition", "fm" ]
suraj520/rf-signal-data
0.77
Convert this spectrum-monitoring sample into a safe incident-note style summary.
capture_file=5ghz_passivescan_background_loc1_9905.csv, capture_frequency_mhz=5180, derived_mean_rssi=5.4, derived_mean_relpwr_db=8.9, derived_mean_avgpwr_db=57.9, derived_mean_magnitude=48.1, class_hint=benign baseline, emitter_hint=background, capture_index=128
Write as if the reader is documenting observations for later technical review.
Incident-note summary: capture `5ghz_passivescan_background_loc1_9905.csv` shows a benign baseline profile near 5180 MHz with mean RSSI 5.4. The emitter hint `background` should be treated as a classification clue, not final proof. Recommended note fields are time, location, receiver setup, repeated-observation status,...
[ "signals", "incident-note", "spectrum-monitoring", "safe-analysis" ]
daniaherzalla/radio-frequency-jamming
0.8
Turn this radio monitoring entry into a short training note for a new amateur operator.
recording=gqrx_20230322_153551_146520000.wav, label=KE6ZGR
Audience: beginner learning simplex monitoring habits.
Training note: a file labeled `KE6ZGR` from a 2-meter simplex monitor is useful for learning how stations appear in logs even before you review the audio. Listen first, identify whether the capture is real traffic or just noise labeling, and remember that calling frequencies are for making contact efficiently rather th...
[ "ham-radio", "training", "simplex", "new-operator" ]
daviddkarnowski/amateur-radio-transmissions-2-meter-fm-simplex
0.75
Explain this RF log entry to a ham operator who wants band and equipment intuition.
frequency_hz=90000000, frequency_mhz=90.000, signal_strength_dbm=-65.0, modulation=FM, bandwidth=100000, device_type=SteamDeck, antenna_type=Directional, weather=Sunny, interference_type=Adjacent-channel, air_pressure=, device_status=Running game, row_index=400
Audience: operator learning how raw RF metadata maps to practical station thinking.
Practical read: 90.000 MHz places the sample in VHF and near the general coverage reference region when that mapping applies. A moderate level with FM and 100000 should be interpreted together, not alone. The Directional antenna and SteamDeck receiver may shape what was captured just as much as propagation does. Treat ...
[ "ham-radio", "signals", "band-intuition", "fm" ]
suraj520/rf-signal-data
0.77
Turn this radio monitoring entry into a short training note for a new amateur operator.
recording=gqrx_20230417_022300_146520000.wav, label=KE6ZGR
Audience: beginner learning simplex monitoring habits.
Training note: a file labeled `KE6ZGR` from a 2-meter simplex monitor is useful for learning how stations appear in logs even before you review the audio. Listen first, identify whether the capture is real traffic or just noise labeling, and remember that calling frequencies are for making contact efficiently rather th...
[ "ham-radio", "training", "simplex", "new-operator" ]
daviddkarnowski/amateur-radio-transmissions-2-meter-fm-simplex
0.75
Predict the most useful next diagnostic checks for this RF measurement.
frequency_hz=140000000, frequency_mhz=140.000, signal_strength_dbm=-95.0, modulation=FM, bandwidth=500000, device_type=SteamDeck, antenna_type=Yagi, weather=Sunny, interference_type=Adjacent-channel, air_pressure=, device_status=Running game, row_index=1142
Answer like a methodical radio engineer reviewing logged metadata.
Recommended checks: 1) verify the receive chain and calibration for a -95.0 dBm reading, 2) confirm whether Adjacent-channel is consistent with nearby occupancy or a local artifact, 3) review whether the Yagi antenna choice fits the target signal geometry, 4) compare this FM sample against neighboring captures on the s...
[ "signals", "diagnostics", "fm", "rf-measurement" ]
suraj520/rf-signal-data
0.79
Classify this indexed RF audio item as likely operator traffic, calling-channel activity, or non-voice artifact.
filename=gqrx_20230419_025141_146520000.wav, callsign_label=KE6ZGR, sample_index=787
Use a monitoring and spectrum-logging viewpoint. Do not invent audio content that is not present in the metadata.
Most likely class: operator traffic or calling-channel voice activity. Reasoning: the label is `KE6ZGR`, the file name looks like a narrowband receive capture, and the context matches amateur simplex monitoring. Next step: check the clip for actual speech, unmodulated carriers, or noise signatures before adding it to a...
[ "ham-radio", "classification", "audio-index", "monitoring" ]
daviddkarnowski/amateur-radio-transmissions-2-meter-fm-simplex
0.73
Explain this RF log entry to a ham operator who wants band and equipment intuition.
frequency_hz=90000000, frequency_mhz=90.000, signal_strength_dbm=-44.0, modulation=AM, bandwidth=200000, device_type=SteamDeck, antenna_type=Directional, weather=Rainy, interference_type=None, air_pressure=, device_status=Running game, row_index=133
Audience: operator learning how raw RF metadata maps to practical station thinking.
Practical read: 90.000 MHz places the sample in VHF and near the general coverage reference region when that mapping applies. A moderate level with AM and 200000 should be interpreted together, not alone. The Directional antenna and SteamDeck receiver may shape what was captured just as much as propagation does. Treat ...
[ "ham-radio", "signals", "band-intuition", "am" ]
suraj520/rf-signal-data
0.77
Explain this RF log entry to a ham operator who wants band and equipment intuition.
frequency_hz=160000000, frequency_mhz=160.000, signal_strength_dbm=-65.0, modulation=AM, bandwidth=50000, device_type=SteamDeck, antenna_type=Yagi, weather=Cloudy, interference_type=Adjacent-channel, air_pressure=, device_status=Running game, row_index=230
Audience: operator learning how raw RF metadata maps to practical station thinking.
Practical read: 160.000 MHz places the sample in VHF and near the general coverage reference region when that mapping applies. A moderate level with AM and 50000 should be interpreted together, not alone. The Yagi antenna and SteamDeck receiver may shape what was captured just as much as propagation does. Treat the int...
[ "ham-radio", "signals", "band-intuition", "am" ]
suraj520/rf-signal-data
0.77
Predict the most useful next diagnostic checks for this RF measurement.
frequency_hz=100000000, frequency_mhz=100.000, signal_strength_dbm=-69.0, modulation=FM, bandwidth=100000, device_type=SteamDeck, antenna_type=Directional, weather=Cloudy, interference_type=Co-channel, air_pressure=, device_status=Running game, row_index=561
Answer like a methodical radio engineer reviewing logged metadata.
Recommended checks: 1) verify the receive chain and calibration for a -69.0 dBm reading, 2) confirm whether Co-channel is consistent with nearby occupancy or a local artifact, 3) review whether the Directional antenna choice fits the target signal geometry, 4) compare this FM sample against neighboring captures on the ...
[ "signals", "diagnostics", "fm", "rf-measurement" ]
suraj520/rf-signal-data
0.79
Interpret this amateur radio recording index entry and explain what it suggests operationally.
filename=gqrx_20230331_210320_146520000.wav, callsign_label=KN6OS
Assume the recordings are from the 2-meter simplex calling area. Focus on lawful amateur operation, observation, and signal classification.
Observation: this looks like amateur station activity. The filename suggests an observation near 146520000 Hz, which is consistent with 2-meter simplex activity when close to 146.520 MHz. If `KN6OS` is a valid amateur callsign, likely use cases include calling, brief coordination, or local conversation rather than repe...
[ "ham-radio", "2m", "simplex", "signal-observation" ]
daviddkarnowski/amateur-radio-transmissions-2-meter-fm-simplex
0.74
Predict the most useful next diagnostic checks for this RF measurement.
frequency_hz=120000000, frequency_mhz=120.000, signal_strength_dbm=-79.0, modulation=QPSK, bandwidth=500000, device_type=HackRF, antenna_type=Directional, weather=Sunny, interference_type=Adjacent-channel, air_pressure=, device_status=Streaming I/Q data, row_index=196
Answer like a methodical radio engineer reviewing logged metadata.
Recommended checks: 1) verify the receive chain and calibration for a -79.0 dBm reading, 2) confirm whether Adjacent-channel is consistent with nearby occupancy or a local artifact, 3) review whether the Directional antenna choice fits the target signal geometry, 4) compare this QPSK sample against neighboring captures...
[ "signals", "diagnostics", "qpsk", "rf-measurement" ]
suraj520/rf-signal-data
0.79
Interpret this RF spectrum capture and explain whether it resembles normal occupancy or a possible interference event.
capture_file=5745mhz_jamming_3dbm_gaussiannoise_675.csv, capture_frequency_mhz=5180, derived_mean_rssi=4.9, derived_mean_relpwr_db=9.4, derived_mean_avgpwr_db=57.8, derived_mean_magnitude=56.9, class_hint=harmful interference candidate, emitter_hint=gaussian_noise, capture_index=71
Respond from a lawful monitoring and interference-analysis perspective only. Do not provide jamming instructions or offensive spectrum abuse guidance.
Spectrum interpretation: this sample looks like a harmful interference candidate. Mean RSSI is 4.9, relative power is 9.4 dB, average power is 57.8, and mean magnitude is 56.9 at approximately 5180 MHz. If elevated power persists across repeated captures, treat it as an interference investigation rather than a transmis...
[ "signals", "interference-analysis", "spectrum-monitoring", "rf-diagnostics" ]
daniaherzalla/radio-frequency-jamming
0.79
Classify this indexed RF audio item as likely operator traffic, calling-channel activity, or non-voice artifact.
filename=gqrx_20230607_185333_146520000.wav, callsign_label=KF7NP, sample_index=907
Use a monitoring and spectrum-logging viewpoint. Do not invent audio content that is not present in the metadata.
Most likely class: operator traffic or calling-channel voice activity. Reasoning: the label is `KF7NP`, the file name looks like a narrowband receive capture, and the context matches amateur simplex monitoring. Next step: check the clip for actual speech, unmodulated carriers, or noise signatures before adding it to a ...
[ "ham-radio", "classification", "audio-index", "monitoring" ]
daviddkarnowski/amateur-radio-transmissions-2-meter-fm-simplex
0.73
Explain this RF log entry to a ham operator who wants band and equipment intuition.
frequency_hz=100000000, frequency_mhz=100.000, signal_strength_dbm=-13.0, modulation=BPSK, bandwidth=50000, device_type=HackRF, antenna_type=Dipole, weather=Cloudy, interference_type=Co-channel, air_pressure=, device_status=Streaming I/Q data, row_index=357
Audience: operator learning how raw RF metadata maps to practical station thinking.
Practical read: 100.000 MHz places the sample in VHF and near the general coverage reference region when that mapping applies. A strong level with BPSK and 50000 should be interpreted together, not alone. The Dipole antenna and HackRF receiver may shape what was captured just as much as propagation does. Treat the inte...
[ "ham-radio", "signals", "band-intuition", "bpsk" ]
suraj520/rf-signal-data
0.77
Interpret this RF spectrum capture and explain whether it resembles normal occupancy or a possible interference event.
capture_file=5180mhz_jamming_9dbm_gaussiannoise_251.csv, capture_frequency_mhz=5180, derived_mean_rssi=5.3, derived_mean_relpwr_db=9.3, derived_mean_avgpwr_db=57.5, derived_mean_magnitude=57.4, class_hint=harmful interference candidate, emitter_hint=gaussian_noise, capture_index=177
Respond from a lawful monitoring and interference-analysis perspective only. Do not provide jamming instructions or offensive spectrum abuse guidance.
Spectrum interpretation: this sample looks like a harmful interference candidate. Mean RSSI is 5.3, relative power is 9.3 dB, average power is 57.5, and mean magnitude is 57.4 at approximately 5180 MHz. If elevated power persists across repeated captures, treat it as an interference investigation rather than a transmis...
[ "signals", "interference-analysis", "spectrum-monitoring", "rf-diagnostics" ]
daniaherzalla/radio-frequency-jamming
0.79
Assess this RF logging record and explain what an engineer should infer from it.
frequency_hz=160000000, frequency_mhz=160.000, signal_strength_dbm=-11.0, modulation=BPSK, bandwidth=200000, device_type=SteamDeck, antenna_type=Yagi, weather=Rainy, interference_type=None, air_pressure=, device_status=Running game, row_index=616
Focus on interpretation, signal quality, propagation context, and instrumentation limitations.
Signal assessment: 160.000 MHz sits in the VHF region and overlaps the general coverage amateur reference band when applicable. The measured level is -11.0 dBm, which is a strong receive level in many monitoring setups. The modulation is BPSK, the antenna is Yagi, the device is SteamDeck, and the reported interference ...
[ "signals", "rf-logging", "bpsk", "measurement-interpretation" ]
suraj520/rf-signal-data
0.78
Turn this radio monitoring entry into a short training note for a new amateur operator.
recording=gqrx_20230404_152723_146520000.wav, label=KN6TMJ
Audience: beginner learning simplex monitoring habits.
Training note: a file labeled `KN6TMJ` from a 2-meter simplex monitor is useful for learning how stations appear in logs even before you review the audio. Listen first, identify whether the capture is real traffic or just noise labeling, and remember that calling frequencies are for making contact efficiently rather th...
[ "ham-radio", "training", "simplex", "new-operator" ]
daviddkarnowski/amateur-radio-transmissions-2-meter-fm-simplex
0.75
Explain this RF log entry to a ham operator who wants band and equipment intuition.
frequency_hz=160000000, frequency_mhz=160.000, signal_strength_dbm=-37.0, modulation=QPSK, bandwidth=50000, device_type=SteamDeck, antenna_type=Dipole, weather=Sunny, interference_type=Adjacent-channel, air_pressure=, device_status=Running game, row_index=1041
Audience: operator learning how raw RF metadata maps to practical station thinking.
Practical read: 160.000 MHz places the sample in VHF and near the general coverage reference region when that mapping applies. A strong level with QPSK and 50000 should be interpreted together, not alone. The Dipole antenna and SteamDeck receiver may shape what was captured just as much as propagation does. Treat the i...
[ "ham-radio", "signals", "band-intuition", "qpsk" ]
suraj520/rf-signal-data
0.77
Interpret this amateur radio recording index entry and explain what it suggests operationally.
filename=gqrx_20230507_091322_146520000.wav, callsign_label=KN6SHI
Assume the recordings are from the 2-meter simplex calling area. Focus on lawful amateur operation, observation, and signal classification.
Observation: this looks like amateur station activity. The filename suggests an observation near 146520000 Hz, which is consistent with 2-meter simplex activity when close to 146.520 MHz. If `KN6SHI` is a valid amateur callsign, likely use cases include calling, brief coordination, or local conversation rather than rep...
[ "ham-radio", "2m", "simplex", "signal-observation" ]
daviddkarnowski/amateur-radio-transmissions-2-meter-fm-simplex
0.74
Convert this spectrum-monitoring sample into a safe incident-note style summary.
capture_file=5ghz_passivescan_background_loc1_10568.csv, capture_frequency_mhz=5180, derived_mean_rssi=5.3, derived_mean_relpwr_db=8.9, derived_mean_avgpwr_db=57.9, derived_mean_magnitude=51.1, class_hint=benign baseline, emitter_hint=background, capture_index=204
Write as if the reader is documenting observations for later technical review.
Incident-note summary: capture `5ghz_passivescan_background_loc1_10568.csv` shows a benign baseline profile near 5180 MHz with mean RSSI 5.3. The emitter hint `background` should be treated as a classification clue, not final proof. Recommended note fields are time, location, receiver setup, repeated-observation status...
[ "signals", "incident-note", "spectrum-monitoring", "safe-analysis" ]
daniaherzalla/radio-frequency-jamming
0.8
Turn this radio monitoring entry into a short training note for a new amateur operator.
recording=gqrx_20230501_052254_146520000.wav, label=KN6HMD
Audience: beginner learning simplex monitoring habits.
Training note: a file labeled `KN6HMD` from a 2-meter simplex monitor is useful for learning how stations appear in logs even before you review the audio. Listen first, identify whether the capture is real traffic or just noise labeling, and remember that calling frequencies are for making contact efficiently rather th...
[ "ham-radio", "training", "simplex", "new-operator" ]
daviddkarnowski/amateur-radio-transmissions-2-meter-fm-simplex
0.75
Classify this indexed RF audio item as likely operator traffic, calling-channel activity, or non-voice artifact.
filename=gqrx_20230404_213733_146520000.wav, callsign_label=KN6OS, sample_index=118
Use a monitoring and spectrum-logging viewpoint. Do not invent audio content that is not present in the metadata.
Most likely class: operator traffic or calling-channel voice activity. Reasoning: the label is `KN6OS`, the file name looks like a narrowband receive capture, and the context matches amateur simplex monitoring. Next step: check the clip for actual speech, unmodulated carriers, or noise signatures before adding it to a ...
[ "ham-radio", "classification", "audio-index", "monitoring" ]
daviddkarnowski/amateur-radio-transmissions-2-meter-fm-simplex
0.73
Assess this RF logging record and explain what an engineer should infer from it.
frequency_hz=100000000, frequency_mhz=100.000, signal_strength_dbm=-69.0, modulation=FM, bandwidth=100000, device_type=Halow-U, antenna_type=Dipole, weather=Rainy, interference_type=None, air_pressure=, device_status=Transmitting beacon signal, row_index=149
Focus on interpretation, signal quality, propagation context, and instrumentation limitations.
Signal assessment: 100.000 MHz sits in the VHF region and overlaps the general coverage amateur reference band when applicable. The measured level is -69.0 dBm, which is a moderate receive level in many monitoring setups. The modulation is FM, the antenna is Dipole, the device is Halow-U, and the reported interference ...
[ "signals", "rf-logging", "fm", "measurement-interpretation" ]
suraj520/rf-signal-data
0.78
Interpret this amateur radio recording index entry and explain what it suggests operationally.
filename=gqrx_20230323_013613_146520000.wav, callsign_label=KN6OS
Assume the recordings are from the 2-meter simplex calling area. Focus on lawful amateur operation, observation, and signal classification.
Observation: this looks like amateur station activity. The filename suggests an observation near 146520000 Hz, which is consistent with 2-meter simplex activity when close to 146.520 MHz. If `KN6OS` is a valid amateur callsign, likely use cases include calling, brief coordination, or local conversation rather than repe...
[ "ham-radio", "2m", "simplex", "signal-observation" ]
daviddkarnowski/amateur-radio-transmissions-2-meter-fm-simplex
0.74
Predict the most useful next diagnostic checks for this RF measurement.
frequency_hz=120000000, frequency_mhz=120.000, signal_strength_dbm=-58.0, modulation=AM, bandwidth=100000, device_type=HackRF, antenna_type=Omnidirectional, weather=Cloudy, interference_type=Adjacent-channel, air_pressure=, device_status=Streaming I/Q data, row_index=130
Answer like a methodical radio engineer reviewing logged metadata.
Recommended checks: 1) verify the receive chain and calibration for a -58.0 dBm reading, 2) confirm whether Adjacent-channel is consistent with nearby occupancy or a local artifact, 3) review whether the Omnidirectional antenna choice fits the target signal geometry, 4) compare this AM sample against neighboring captur...
[ "signals", "diagnostics", "am", "rf-measurement" ]
suraj520/rf-signal-data
0.79
Assess this RF logging record and explain what an engineer should infer from it.
frequency_hz=70000000, frequency_mhz=70.000, signal_strength_dbm=-31.0, modulation=QPSK, bandwidth=200000, device_type=HackRF, antenna_type=Omnidirectional, weather=Cloudy, interference_type=Co-channel, air_pressure=, device_status=Streaming I/Q data, row_index=210
Focus on interpretation, signal quality, propagation context, and instrumentation limitations.
Signal assessment: 70.000 MHz sits in the VHF region and overlaps the general coverage amateur reference band when applicable. The measured level is -31.0 dBm, which is a strong receive level in many monitoring setups. The modulation is QPSK, the antenna is Omnidirectional, the device is HackRF, and the reported interf...
[ "signals", "rf-logging", "qpsk", "measurement-interpretation" ]
suraj520/rf-signal-data
0.78
Predict the most useful next diagnostic checks for this RF measurement.
frequency_hz=90000000, frequency_mhz=90.000, signal_strength_dbm=-38.0, modulation=AM, bandwidth=1000000, device_type=SteamDeck, antenna_type=Directional, weather=Sunny, interference_type=Co-channel, air_pressure=, device_status=Running game, row_index=573
Answer like a methodical radio engineer reviewing logged metadata.
Recommended checks: 1) verify the receive chain and calibration for a -38.0 dBm reading, 2) confirm whether Co-channel is consistent with nearby occupancy or a local artifact, 3) review whether the Directional antenna choice fits the target signal geometry, 4) compare this AM sample against neighboring captures on the ...
[ "signals", "diagnostics", "am", "rf-measurement" ]
suraj520/rf-signal-data
0.79
Classify this indexed RF audio item as likely operator traffic, calling-channel activity, or non-voice artifact.
filename=gqrx_20230611_203015_146520000.wav, callsign_label=KE6PLA, sample_index=157
Use a monitoring and spectrum-logging viewpoint. Do not invent audio content that is not present in the metadata.
Most likely class: operator traffic or calling-channel voice activity. Reasoning: the label is `KE6PLA`, the file name looks like a narrowband receive capture, and the context matches amateur simplex monitoring. Next step: check the clip for actual speech, unmodulated carriers, or noise signatures before adding it to a...
[ "ham-radio", "classification", "audio-index", "monitoring" ]
daviddkarnowski/amateur-radio-transmissions-2-meter-fm-simplex
0.73
Predict the most useful next diagnostic checks for this RF measurement.
frequency_hz=160000000, frequency_mhz=160.000, signal_strength_dbm=-54.0, modulation=QPSK, bandwidth=100000, device_type=Halow-U, antenna_type=Directional, weather=Rainy, interference_type=Co-channel, air_pressure=, device_status=Transmitting beacon signal, row_index=630
Answer like a methodical radio engineer reviewing logged metadata.
Recommended checks: 1) verify the receive chain and calibration for a -54.0 dBm reading, 2) confirm whether Co-channel is consistent with nearby occupancy or a local artifact, 3) review whether the Directional antenna choice fits the target signal geometry, 4) compare this QPSK sample against neighboring captures on th...
[ "signals", "diagnostics", "qpsk", "rf-measurement" ]
suraj520/rf-signal-data
0.79
Predict the most useful next diagnostic checks for this RF measurement.
frequency_hz=140000000, frequency_mhz=140.000, signal_strength_dbm=-3.0, modulation=8PSK, bandwidth=50000, device_type=HackRF, antenna_type=Dipole, weather=Cloudy, interference_type=Adjacent-channel, air_pressure=, device_status=Streaming I/Q data, row_index=539
Answer like a methodical radio engineer reviewing logged metadata.
Recommended checks: 1) verify the receive chain and calibration for a -3.0 dBm reading, 2) confirm whether Adjacent-channel is consistent with nearby occupancy or a local artifact, 3) review whether the Dipole antenna choice fits the target signal geometry, 4) compare this 8PSK sample against neighboring captures on th...
[ "signals", "diagnostics", "8psk", "rf-measurement" ]
suraj520/rf-signal-data
0.79
Predict the most useful next diagnostic checks for this RF measurement.
frequency_hz=160000000, frequency_mhz=160.000, signal_strength_dbm=-74.0, modulation=QPSK, bandwidth=100000, device_type=SteamDeck, antenna_type=Yagi, weather=Sunny, interference_type=Co-channel, air_pressure=, device_status=Running game, row_index=759
Answer like a methodical radio engineer reviewing logged metadata.
Recommended checks: 1) verify the receive chain and calibration for a -74.0 dBm reading, 2) confirm whether Co-channel is consistent with nearby occupancy or a local artifact, 3) review whether the Yagi antenna choice fits the target signal geometry, 4) compare this QPSK sample against neighboring captures on the same ...
[ "signals", "diagnostics", "qpsk", "rf-measurement" ]
suraj520/rf-signal-data
0.79
End of preview.
README.md exists but content is empty.
Downloads last month
12