Shadow (Feb 11 2009) |
![]() |
| log in |
Message boards : Technical News : Shadow (Feb 11 2009)
| Author | Message |
|---|---|
|
Before releasing the astropulse application Eric had to add a couple fields to the result tables in the science database that are now necessary. These are large fields, and it's taking informix forever to update the table. The job was started 24 hours ago and is still chugging along. I guess it doesn't help that the assimilator queue is still rather large (though it is draining). So the release is delayed until this job finishes. | |
| ID: 864445 · | |
|
Thanks for the update Matt. Gives the optimizing crew a little more time to get ready for the new APs. :) | |
| ID: 864457 · | |
Before releasing the astropulse application Eric had to add a couple fields to the result tables in the science database that are now necessary. These are large fields, and it's taking informix forever to update the table. The job was started 24 hours ago and is still chugging along. I guess it doesn't help that the assimilator queue is still rather large (though it is draining). So the release is delayed until this job finishes. Do you use any data substitution on server-side data cleanup (I mean, do you insert something in data array instead of removed radar pulses ? ) If yes, is it possible to mark these "blanked" areas in task header so client could know what areas are "true" ones and what contain some substituted stub data? Some list of indexes of blanked regions for example... | |
| ID: 864612 · | |
|
| |
| ID: 864615 · | |
...so the client could skip those? ____________ mic. | |
| ID: 864634 · | |
The radar blanking stuff... What angle are you going for? My scraps of understanding from previous posts are that there is a radar detector on the telescope at Arecibo. The output from that is recorded on a spare data recorder channel in parallel to the 14 streams of radio data. Matt's code then substitutes psuedo-random random noise into the data stream to replace the radar mess whenever the radar has been detected. The psuedo-random noise then goes innocently through the rest of the data processing as though Arecibo hasn't heard anything other than the usual background noise. The radar source is a nearby military radar. The radar is kindly blanked for the arc sweeping Arecibo. However, that doesn't stop reflections that bounce off aircraft (or other local structures?) splattering Arecibo... Perhaps: Also set aside an air exclusion zone around Arecibo? Change the radar frequency to something much higher than the Arecibo receivers? (Or will the radar ERP saturate anything more sensitive than an AC power rectifier diode?!) An interesting question is whether Matt has had to add any cleverness to avoid a signal spike being detected by the FFT for the transition to/from the psuedo-random noise section...? I would expect the FFT to "see" the transition in the noise "texture". Happy crunchin', Martin ____________ Mandriva Linux A user friendly OS! See new freedom Mageia2 The Future is what We make IT (GPLv3) | |
| ID: 864647 · | |
|
Can anyone comment on the mathematical correctness of adding pseudorandom noise? | |
| ID: 864672 · | |
|
Matt, | |
| ID: 864753 · | |
Change the radar frequency to something much higher than the Arecibo receivers? (Or will the radar ERP saturate anything more sensitive than an AC power rectifier diode?!) If it is a ground based radar it likely will saturate even the power diode. Heck, when I worked on OTH-B ... when we radiated on a frequency no one in the world could use that slot ... the good news is that it was low frequency so most people could not care less ... but it was funny working with the Radar Control guys ... we would suggest a frequency band and they would find a clear spot and then "park" the radar there with short scans before changing the whole system over ... they kinda played nice by reserving the space before stepping on anyone that had had an idea of coming up on that spot ... | |
| ID: 864844 · | |
|
Well, short question is: | |
| ID: 864996 · | |
|
I think they archive all raw data. If so the software blanking could in principle be modified in the future and the data re-processed. | |
| ID: 865017 · | |
I think they archive all raw data. If so the software blanking could in principle be modified in the future and the data re-processed. Too much unneeded work to rely on this archived datas. In general, if there is some way not to do smth, better use it as soon as possible ;) | |
| ID: 865088 · | |
Message boards : Technical News : Shadow (Feb 11 2009)
| Copyright © 2013 University of California |