How much common work is there for clients, when doing first an AP job and then several MB jobs from the data now split by the servers?

The data has to be converted to ones and minus ones, chirped (rotated), fft'd and dechirped (rebuilt), pulses must be searched, averages and powers calculated...

I'm wondering if it would be of any help for the project, if an AP data chunk, already preprocessed by (and sent to) the end user machine could be utilised as a source for any extra calculations needed by the MB work. The client preprocessed AP packet would produce multiple MB results requiring some additional (gaussFit, autocorr, ... work) - would it?

Though I might be totally wrong. This was just a thought that popped into my mind just before falling asleep. Had to write it down.

---

To overcome Heisenbergs:
"You can't always get what you want / but if you try sometimes you just might find / you get what you need." -- Rolling Stones

MB does doppler effect correction(narrow signal) while AP does dedispersion (wide freq range, narrow signal doesn't disperse). Both use freq domain for that but MB uses different freq width from 8 to 128k bins (how those bins translated into freq range in Hz is separate question) while AP uses fixed 32k FFT. Not much if any at all common parts. Also, AP blanking can ruin any similarities on FFT level if they would even exist.

---

SETI apps news
We're not gonna fight them. We're gonna transcend them.

OK, thanks.

---

To overcome Heisenbergs:
"You can't always get what you want / but if you try sometimes you just might find / you get what you need." -- Rolling Stones