plows-iss1: Logbook Entries

plows-iss1: RADAR Messages: 4 Entries..

Return to Logbook Contents Page
Entry Date Title Site Author #Graphics
50 Mon 15-Feb-2010NIMA processing errorMISSBill
29 Wed 18-Nov-2009Profiler Parameter SettingsMISSBill
20 Sat 07-Nov-2009POP errors and mode changeMISSBill
18 Thu 05-Nov-2009POP errorsMISSGary


50: RADAR, Site MISS, Mon 15-Feb-2010 09:49:10 GMT, NIMA processing error
NIMA is reporting an error and not producing output or web plots.

Raw spectral data is copying to data manager correctly.  Parameters are unchanged from previous IOPs and SOAP moment data looks fine so the profiler appears to be running fine.

Manually ran NIMA in verbose mode and found that it is reporting a segmentation error:

/iss/nima/etc/spcnima: line 141: 19885 Segmentation fault      nice -19 $valgrind $wppp $args

(Emailed details to Gary)

This error is delaying some of the web page plots, however xsoap plots look fine (emailed a couple to Bob) so we should be able to recover plots in post-processing.


29: RADAR, Site MISS, Wed 18-Nov-2009 02:07:04 GMT, Profiler Parameter Settings
PROFILER PARAMETER SETTINGS

The Profiler is running with the following (single mode) parameter set:

IPP  	 70 microsecs
PW   	 700 ns
Code	 4

Nhgts 	 75
Delay	 2700 ns
Space	 700 ns
Coh.Av	 60
Spe.Av	 26
Npts  	 128

Scale	 19.5 m/s
Dwell	 20 s
Hgt  	 0.24 km
	 8.01 km
IPP  	 9.91 km
Pulse	 105 m

Beam Sequence (all 1 rep): yV22 y+38 x+25 xV21 y-26 x-37

Full spectra saved.
Spectral avg: ICRA
DC filter and windowing
Clutter search to 1.7 km
Cns Avg 30 minutes, 55% thld, window: 2m/s (oblq), 1.5 ms/ (vert). Vert subtract.
No RASS.

Spectra are additionally processed with NIMA.


20: RADAR, Site MISS, Sat 07-Nov-2009 21:55:49 GMT, POP errors and mode change
POP reported errors again. 

19:13 POP reported :

FIFO READ ERROR WORD #1: 20e00 3e00
PAR SET #2 AT 120000NS

Did a Ctrl-Alt_del to get out of POP.  Restarted POPO and got the same error.

Switched to PLOWS-IOP mode (105 m mode) - it had been in alternating 60/250m mode.  Restarted POP - got a different error message:

CANNOT START PBX - CONTINUE ANYWAY?

Entering Y kept giving the same error message so shutdown profiler computer and interface boxes.

It was rather warm in the container so turned on AC and let it cool down for a while.

Restarted the profiler and seems to be running okay now.


18: RADAR, Site MISS, Thu 05-Nov-2009 19:07:09 GMT, POP errors
Today POP was interrupted with errors.  Over a period of about 30 minutes, there were 4 occasions where it had to be restarted, then it ran for an hour or more until we shut it down.  Here's the error messages:

The first was at 2009-11-05 09:30:43:

FIFO read error word #1: 2e00 3e00
Sampling did not finish in 5 seconds, flag = -1
:PAR SET #3 at 120000 ns

The error messages were basically the same each time, except sometimes it was this line:

:PAR SET #3 at 180000 ns

On one occasion, POP eventually recovered from the error and continued normally.  The other times, POP had to be killed through the Windows task manager, and the PC had to be power cycled.

No other symptoms or indications were noticed.  Temperature in the cabin seemed fine, but we didn't feel the PC for excess heat.

Lou suggests upper temperature limit in container be 50 degrees F.  I think that means he's volunteering to operate the rest of the project.