A big change in the frequency & how data is shared -

Hi Steve, 

I'm sorry but I'm not fully understanding what you are saying.

Say for example data for 3 jobs during a one night session on a Syndicate pier is collected, 0.67 hours on one job, 1.9 hours on another and 3.5 hours on the third, will all those be made available within 24 hours? I'm assuming that is the case otherwise it wouldn't be much different to what takes place at present, however, :( :( :(

Hope trip went off okay. 

Cheers, 

Ray 

Yes Ray, what ever data is collected on lets say the evening of 1st/2nd of December with will be automatically shared on the morning/afternoon of the 1st of December

Steve

Hi Steve 

Thanks for clearing up any misunderstanding that I had.

I'll leave it up to other people to express any concerns they may have about the change and so save me from having to do so. 

Hope you got/get back okay.

Regards 

Ray 

I think this could be a nice improvement...  Would reduce the download sizes and help ensure that we get all the frames while the target is still in the arc, without having to wait for 100% completion before requesting our retakes. 

The only concern would be confusion lol, keeping track of the frames collected / re-requested etc...  But perhaps if we added a column to the joblist queue to show how much data had been made available for download (eg amount completed = 70%, uploaded = 70% or whatever) this wouldn't be too hard to manage.

I think this could be a nice improvement...  Would reduce the download sizes and help ensure that we get all the frames while the target is still in the arc, without having to wait for 100% completion before requesting our retakes. 

The only concern would be confusion lol, keeping track of the frames collected / re-requested etc...  But perhaps if we added a column to the joblist queue to show how much data had been made available for download (eg amount completed = 70%, uploaded = 70% or whatever) this wouldn't be too hard to manage.

We can only do so much with the software I am afraid without stupid amounts of coding, which is why I suggested that any data jobs that are put in to replace bad frame a note is added to state it's a retake for frames on Job XXX

We could also post under the section on the forum in the link below

https://www.roboscopes.com/index.php/forum/dataset-suggestions-all

Or, alternatively use the dedicated section for your pier in Discord

I agree, data share as it's collected is a much more efficient way of doing this and keeping on top of things. However, as far as syndicates go, it may need members to "talk" to one another more in all fairness, so everybody knows what's happening :)

Steve

Thanks Anunnaki for starting the ball rolling and some suggestions, and I now see someone has recently replied to you. 

I was somewhat horrified when I first read this post and needed confirmation that I had interpreted it correctly. Having spent a bit of time thinking about it I had 2 suggestions, one of which I won't mention here for fear of getting banned. :) 

I understand the need to address the problems arising from long stretches of bad weather, and whatever approach is taken more monitoring and administration will be involved. 

With the current suggestion it is imperative that for downloaded data the originator of the job scans it asap and notes the number of frames that need replacing. Resubmit a new job to collect the replacement data immediately or on a wait and see basis? 

What I assume people do is occasionally look at the job queue to see how their jobs and others are progressing. Without a rewrite I cannot see how that queue will be able to show accurate information on longer jobs with the suggested change. There could be more than one job for retakes and the job queue does not display the submission notes. At present the replacement subs are submitted in a new job where progress can be easily seen.

My suggestion. Submit new jobs in small chunks except if it is just for a few hours. If you know that most of the data for a short job of yours has been collected but some time has elapsed since then, then you need to contact Roboscopes. 

For longer jobs submit a string of short ones each of 1,2 or possibly 3 hours maximum. If the job is both broadband and narrowband then best split it by filter type. Many already do this anyway. At the time of entering these smaller jobs there is a good chance that the job numbers will be consecutive keeping them grouped together in the queue. In the target description, as was done with mosaics, add a sequence number to make it clearer to others.

No changes required except in how users submit longer jobs.

Hopefully my last word on this unless provoked into responding. :) 

Cheers and CS, 

The old grump.