MBv7 re-observation of MBv6 processed data - optimization is possible?

Message boards : Number crunching : MBv7 re-observation of MBv6 processed data - optimization is possible?
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile Raistmer
Volunteer developer
Volunteer tester
Avatar

Send message
Joined: 16 Jun 01
Posts: 6325
Credit: 106,370,077
RAC: 121
Russia
Message 1674220 - Posted: 5 May 2015, 22:04:36 UTC
Last modified: 5 May 2015, 22:06:37 UTC

As I understand, current tapes were processed by MultiBeam v6 and now get re-process with MultiBeam v7. Is it right?
ID: 1674220 · Report as offensive
Richard Haselgrove Project Donor
Volunteer tester

Send message
Joined: 4 Jul 99
Posts: 14650
Credit: 200,643,578
RAC: 874
United Kingdom
Message 1674236 - Posted: 5 May 2015, 22:29:44 UTC - in response to Message 1674220.  

As I understand, current tapes were processed by MultiBeam v6 and now get re-process with MultiBeam v7. Is it right?

And have been doing for several months. I get asked periodically why no new tapes have appeared in the SETI data distribution history. No new tapes (disks, actually) are known to have been received from Arecibo since 5 December 2014, and we'd processed all those before the turn of the year.
ID: 1674236 · Report as offensive
Profile Raistmer
Volunteer developer
Volunteer tester
Avatar

Send message
Joined: 16 Jun 01
Posts: 6325
Credit: 106,370,077
RAC: 121
Russia
Message 1674316 - Posted: 6 May 2015, 6:23:57 UTC - in response to Message 1674236.  

Then lets recall in what SETI MB v7 is different from v6?
Only Autocorrelation?
ID: 1674316 · Report as offensive
Josef W. Segur
Volunteer developer
Volunteer tester

Send message
Joined: 30 Oct 99
Posts: 4504
Credit: 1,414,761
RAC: 0
United States
Message 1674385 - Posted: 6 May 2015, 15:36:03 UTC - in response to Message 1674316.  

Then lets recall in what SETI MB v7 is different from v6?
Only Autocorrelation?

Yes.

If the project wanted to, they could use an analysis_cfg for these reruns which specified processing only the 128K FFT length with a single chirp limit of 30. That would give them the added Autocorrs with a minimum of redundant signal searches. All tasks would be extreme shorties (AR would make no difference). All dedicated crunchers would be screaming because they couldn't get enough work.

However, there's another reason to reprocess those tapes, the switch to PFB splitting is supposed to be providing cleaner data. I suspect that's more important to the science.
                                                                   Joe
ID: 1674385 · Report as offensive
kittyman Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 9 Jul 00
Posts: 51468
Credit: 1,018,363,574
RAC: 1,004
United States
Message 1674401 - Posted: 6 May 2015, 16:35:51 UTC - in response to Message 1674236.  
Last modified: 6 May 2015, 16:37:26 UTC

As I understand, current tapes were processed by MultiBeam v6 and now get re-process with MultiBeam v7. Is it right?

And have been doing for several months. I get asked periodically why no new tapes have appeared in the SETI data distribution history. No new tapes (disks, actually) are known to have been received from Arecibo since 5 December 2014, and we'd processed all those before the turn of the year.

I am curious about this as well.
Are we not getting new data from Arecibo? If not, why not?
I am not sure what the usual turn around time for a box of drives from Arecibo has been in the past.

Or have we been getting more data but just not rolling it out due to unresolved database issues?
"Freedom is just Chaos, with better lighting." Alan Dean Foster

ID: 1674401 · Report as offensive
Profile HAL9000
Volunteer tester
Avatar

Send message
Joined: 11 Sep 99
Posts: 6534
Credit: 196,805,888
RAC: 57
United States
Message 1674433 - Posted: 6 May 2015, 18:25:22 UTC - in response to Message 1674401.  
Last modified: 6 May 2015, 18:26:37 UTC

As I understand, current tapes were processed by MultiBeam v6 and now get re-process with MultiBeam v7. Is it right?

And have been doing for several months. I get asked periodically why no new tapes have appeared in the SETI data distribution history. No new tapes (disks, actually) are known to have been received from Arecibo since 5 December 2014, and we'd processed all those before the turn of the year.

I am curious about this as well.
Are we not getting new data from Arecibo? If not, why not?
I am not sure what the usual turn around time for a box of drives from Arecibo has been in the past.

Or have we been getting more data but just not rolling it out due to unresolved database issues?

It was mentioned when the got the last shipment of data that is was only a partial full box of drives. Which they only did because we were out of data to split at the time.
It could be that whomever is paying for the time at Arecibo is doing something that is incompatible with the recording data for us. Such as looking for near Earth objects that may impact the planet.
There is a site that lists the scheduled activity for Arecibo. Which might give a hint as to how much they have been able to record.
SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[
ID: 1674433 · Report as offensive
Profile Brent Norman Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester

Send message
Joined: 1 Dec 99
Posts: 2786
Credit: 685,657,289
RAC: 835
Canada
Message 1674554 - Posted: 7 May 2015, 3:19:51 UTC

There was talk about v8 of SETI

I think they are trying to get all the old data processed with the latest ap before they change anything.
ID: 1674554 · Report as offensive

Message boards : Number crunching : MBv7 re-observation of MBv6 processed data - optimization is possible?


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.