Entry
| Date
| Title
| Site
| Author
| #Graphics
|
95 | Thu 26-Oct-2000 | MAPR Status 26 October 2000 | vtmx | iss
|
91 | Thu 26-Oct-2000 | MAPR tape backup failed | vtmx | Mike
|
84 | Wed 25-Oct-2000 | Russian Data, starting the regular sampling mode now and comments about the over sampling | vtmx | Mike
|
83 | Wed 25-Oct-2000 | RASS enabled and disabled | vtmx | Mike
|
81 | Wed 25-Oct-2000 | A-E test has to be redone with NCI set to 200 | vtmx | Mike
|
80 | Tue 24-Oct-2000 | testing for SNR line in the middle alt | vtmx | Mike
|
79 | Tue 24-Oct-2000 | RASS enabled, A & E data, now started till tomorrow, NOT! huge amounts of data here!!! ouch! stopped at 0:53 25 Oct | vtmx | Mike
|
77 | Tue 24-Oct-2000 | Min Pulse Width 200ns | vtmx | Mike
|
75 | Mon 23-Oct-2000 | Starting MAPR range cal w/ Taos soon | vtmx | Mike
|
69 | Fri 20-Oct-2000 | A & E meas, pulse length is only rated down to 200 ns | vtmx | Mike
|
66 | Fri 20-Oct-2000 | MAPR Data backup, IOP7, start 0700 UTC | vtmx | Tian
|
61 | Thu 19-Oct-2000 | started tms collection | vtmx | Lou
|
60 | Thu 19-Oct-2000 | MAPR computer completely locked up while unattended | vtmx | Lou
|
59 | Wed 18-Oct-2000 | Lookin for the middle line | vtmx | Mike
|
55 | Wed 18-Oct-2000 | MAPR Data backup, IOP6, start 0700 UTC | vtmx | Tian
|
51 | Wed 18-Oct-2000 | Start time series collection for IOP6 | vtmx | Tian
|
47 | Tue 17-Oct-2000 | End time series collection and return to vtmx mode, also do a backup | vtmx | Mike
|
43 | Tue 17-Oct-2000 | MAPR Data backup, IOP5, end 0900 UTC | vtmx | Tian
|
32 | Sun 15-Oct-2000 | MAPR time series for IOP3 turned on late | vtmx | Mike
|
15 | Sat 07-Oct-2000 | MAPR TMS collection off and back on | vtmx | Mike
|
- 95: RADAR, Site vtmx, Thu 26-Oct-2000 23:20:54 GMT, MAPR Status 26 October 2000
Generator change required all systems to be shut down.
All systems back up and running by 1PM local (19Z)
Ran vtmx2mode collecting time series and correlations
until 2324Z. (Sodar also running)
Switched to vtmx2mode only collecting correlations as
per conversations with Bill Brown.
- 91: RADAR, Site vtmx, Thu 26-Oct-2000 12:19:51 GMT, MAPR tape backup failed
Tested the tape for files properly copied and it reported too many errors. Cleaned the tape drive and copied the files back into the /data/mapr/ directory and restarted the backup.
- 84: RADAR, Site vtmx, Wed 25-Oct-2000 20:48:54 GMT, Russian Data, starting the regular sampling mode now and comments about the over sampling
starting the 30 gate mode at 20:55 25 Oct
Stopped the Praskov mode at 23:32, had a crash in the
middle.
From Charlie,
Yep, it looks like the Praskov configuration will generate
about 2 GB/hour. For the 40 gate mode, it is
2.3 GB/hour. For the 30 gate mode, it would be
1.7 GB/hour. All other computing in ATD will have
to stop while they analyze this.
I didn't see the problem with the schedule not
working. Your mode vtmxwind1 has 30 gates
and vtmxwind2 has 40 gates. Looking at
the tms files, I see the following:
24-oct 21_45 30 gates
24-oct 22_00 40
24-oct 22_15 40
24-oct 22_30 40
24-oct 22_45 40
24-oct 23_00 40
24-oct 23_15 40
24-oct 23_30 40
24-oct 23_45 40
25-oct 00_00 30
25-oct 00_15 30
So I think that the tms files show a two hour cycling of the mode. Maybe
the mode label in mapr display is not working.
I think they were looking for nci =66 for both test cases. It looks
like
vtmxwind1 has nci=200.
The NCI is now changed.
- 83: RADAR, Site vtmx, Wed 25-Oct-2000 19:14:55 GMT, RASS enabled and disabled
RASS has been enabled for 25 minutes of wind and 5 minutes of RASS
through the scheduler at 25 Oct 19:15. Using ARMISS to generate the
sound and MAPR to collect the data.
RASS ran sucessfully for a few dwells and then crashed. Disabling
now at 20:46 25 oct.
- 81: RADAR, Site vtmx, Wed 25-Oct-2000 17:22:47 GMT, A-E test has to be redone with NCI set to 200
NCI set to 200 for set one and it needs to be reset to 66, set 2
was set to 66..... Will rerun test for mode one again today, mode
2 done.
- 80: RADAR, Site vtmx, Tue 24-Oct-2000 19:39:40 GMT, testing for SNR line in the middle alt
Set the codes from 2 to 1 at 19:30 to run for an hour and then
look to see if the signal plot shows a middle line. Ending test at
20:34 and looking at the signal plot. It does appear that the line
in the middle has dissapeared from the signal level time graph.
- 79: RADAR, Site vtmx, Tue 24-Oct-2000 18:05:42 GMT, RASS enabled, A & E data, now started till tomorrow, NOT! huge amounts of data here!!! ouch! stopped at 0:53 25 Oct
I have attached a cord from the sun-ws head phone jack to the
audio amp and RASS should be ready to run.
If there is no IOP I will start up Alex and Elenores data taking
experiment in the multimode format. I have replaced lo and hi
with 1 and 2 for the 2 modes. If there is an IOP I still might
take an hour of the data.
Started the AE stuff at 21:18 24 Oct 2000, currently looks like
really good data from 700 m to 900 m. in the spectra. Holy shite,
every 15 minutes its collecting 555M in .tms files!!! holy bad
dung!!!!
Stopped taking data because it is just to large. Stopped at 0:53
0
-20
30
32
30e-6
32
192
0
176
130
1
0
0
200
16
128
16
200
512
1
2
30
12
1
1
1
1
0
1
1
./a_and_e
hanning
0
-20
30
32
30e-6
4
192
0
176
130
1
0
0
200
16
128
16
66
512
1
2
40
12
1
1
1
1
0
1
1
./a_and_e
hanning
- 77: RADAR, Site vtmx, Tue 24-Oct-2000 17:40:39 GMT, Min Pulse Width 200ns
Min pulse width for the final amp is 200 ns or 10 counts.
PIRAQ has been run at 4 counts spacing w/o finding a problem
at this point.
- 75: RADAR, Site vtmx, Mon 23-Oct-2000 20:57:45 GMT, Starting MAPR range cal w/ Taos soon
Time now 23 Oct 20:58 UTC
stoppped at 23 Oct 23:30ish UTC
- 69: RADAR, Site vtmx, Fri 20-Oct-2000 10:17:27 GMT, A & E meas, pulse length is only rated down to 200 ns
> > I talked with Alex about the sample data
> > sets that he and Eleanor would like to get from
> > Mapr. There are two scenarios that they
> > are interested in. The first is basically the
> > same sample mode that the system
> > is currently running in, except with a higher
> > sample frequency, obtained by decreasing NCI:
> >
> > prf 30uSec
> > ncib 66
> > points 512
> > nspec 12
> > space 32 (100m)
> > width 32 (100m)
> > gates 30
> >
> > The second scheme then decreases the gate
> > spacing to 25m:
> >
> > prf 30 uSec
> > nci 66
> > points 512
> > nspec 12
> > space 8 (25m)
> > width 8 (25m)
> > gates 40
> >
> > They would like two hours of data for each scheme. They
> > are aware that this measurement will need to be made on a
> > non-IOP day. I suggested that you start the measurements
> > in the afternoon after you have gotten a good profile that
> > indicates that a good run of Mapr observations is
> > starting (as its normal afternoon behavior), and
> > run for 4 hours, doing the first test followed by the
> > second one.
addnl:
Alex grabbed me today and refined his request for
the mapr data that they would like. In particular,
he wants to oversample on the second test, so we
leave the xmit pulse at 100m, and set the gate width
as small as possible (here 12.5m)
We have never tested a 12.m gate width, so
don't be surprised if something funny seems to
happen - it would be related to the MAC
unit on piraq being switched that quickly.
Also, since the gate spacing is going to be so
fine, I would move the first gate up so
it is is in the region where we seem to
have been getting reasonable winds, say
600m. Otherwise most of their data will be
in that suspicious 100m-400m region.
One other thing - Alex requested that pulse coding
be turned off for this data - i.e. code = 1
- 66: RADAR, Site vtmx, Fri 20-Oct-2000 07:08:44 GMT, MAPR Data backup, IOP7, start 0700 UTC
Data backup of IOP7 starts at 0700 UTC
- 61: RADAR, Site vtmx, Thu 19-Oct-2000 22:04:34 GMT, started tms collection
Started time series saving at 22:03 gmt
- 60: RADAR, Site vtmx, Thu 19-Oct-2000 21:18:18 GMT, MAPR computer completely locked up while unattended
Radar pc had locked up at 1:18 local 10-19-2000
Rebooted at approx 3:20 local on the 19th
Had to do a reset on the computer to reboot it
- 59: RADAR, Site vtmx, Wed 18-Oct-2000 20:44:29 GMT, Lookin for the middle line
Because there is a pretty solid line in the signal plots
at about the halfway point I have changed the PW to 50m and
the number of gates to 40. This should put the line at 1
km if it is related to the fact that the gates are split
in processing. SABL has a problem when it comes to 2 DSPs
in that they don't read exactly the same power level so they
produce some banding. The software written to the DSPs may
be perfect, but they might read a little dif and that makes
the line.
The change happened at about 20:15 and will change back in a
couple of hours.
- 55: RADAR, Site vtmx, Wed 18-Oct-2000 07:04:59 GMT, MAPR Data backup, IOP6, start 0700 UTC
Data backup of IOP6 starts at 0700 UTC
- 51: RADAR, Site vtmx, Wed 18-Oct-2000 01:46:42 GMT, Start time series collection for IOP6
Start vtmx2mode and time series collection at approximately 2300 UTC
and switch to vtmx at approximately 2320 UTC
- 47: RADAR, Site vtmx, Tue 17-Oct-2000 17:10:16 GMT, End time series collection and return to vtmx mode, also do a backup
Ended vtmx2mode and time series collection, started just vtmx
because the signal and SNR plots are confusing. Want to check
signal level with extra amp in blue(3) channel.
Backup started 15:17 UTC 17 Oct 00
It appears as though the lower gates are getting shifted to
middle of the screen. Symetric spurs are in the middle gates.
Called Charlie and emailed Bill.
- 43: RADAR, Site vtmx, Tue 17-Oct-2000 11:23:20 GMT, MAPR Data backup, IOP5, end 0900 UTC
Data backup of IOP5, first tape, tape ends 0900UTC, also cleaned the
exabyte tape drive.
- 32: RADAR, Site vtmx, Sun 15-Oct-2000 10:32:19 GMT, MAPR time series for IOP3 turned on late
The time series were forgotten till about 8pm LTC.
- 15: RADAR, Site vtmx, Sat 07-Oct-2000 17:26:04 GMT, MAPR TMS collection off and back on
TMS collection terminated at 17;26 GMT FOR MAPR.
Back on for IOP 3 at 22:00 GMT