Greg Jones replied to the topic 'EKOS imaging pipeline?' in the forum. 6 years ago

knro, I can make that work in theory, but it dosn't do what I am looking for.

Think remote observatory with slow data connection. We shoot about 5000 frames per target and 10+ targets an hour. We can fill a terabyte drive in 3 nights. So the goal is to collect the raw frames in the observatory and do the Speckle reduction (Fourier based) on the fly (GPU) returning just the Speckle results. That will give us close to a 5000 to 1 reduction in data needing to be transferred. We also need to put the files into a reasonable directory structure and Ideally store each target in a FITs cube instead of a frame per file.

I know that's a lot and I'll take a shot at it. Since the first note I've looked at the code and have an idea what to do.

TIt looks like EKOS does the actual file save, correct? That means that EKOS would need to be running on the observatory computer. If all that is correct, then splitting the scheduler from the capture module would be the Ideal way forward. That is, let the capture module run under the server, and direct it with the scheduler via the server.

Hope that makes sense?

I'm hoping to get the cuda/GPU portion working, probably with Open Astro, but CCDCiel is also a possibility as it uses INDI for the cameras from what I can tell.

Thank you,

Read More...