PIER-14 Data prioritization - New settings!

hello Steve 

in your priotization setting , can you priotize old jobs ? 

it ssems that some old jobs are not done before newer ones , and make very difficult to follow progress and redo . 
for example these jobs 
[table]001156 p14 Rosette 9611197.93h33.3%
001194 p14 ic443 10761608.00h25.0%
001240 p14 ngc2175 8361105.50h28.6%
001241 p14 tadpole neb 110830012.00h66.7%
001253 p14 M42 961962.33h42.9%
001254 p14 M42 9611564.98h91.7%[/table]


some are scheduled since august . I think that old one should be shoot in priority

Hi steve , 

i m sorry to insist , but there is something i cant understand 

Why old jobs are not processed before new one ? 

i ve submit a job last week , RGB part of IC405 , job 1439,  It as been already process but old one as 1156, rosette job, scheduled on August , are still stuck . 

The object M42 , rosetta , tadpole ,ic443 , are scheduled since a very long time and not process before the newer one .  These object are going to be off quicky , and jobs wont be finish....

regards, 

florent

Hi steve , 

i m sorry to insist , but there is something i cant understand 

Why old jobs are not processed before new one ? 

 

i ve submit a job last week , RGB part of IC405 , job 1439,  It as been already process but old one as 1156, rosette job, scheduled on August , are still stuck . 

 

The object M42 , rosetta , tadpole ,ic443 , are scheduled since a very long time and not process before the newer one .  These object are going to be off quicky , and jobs wont be finish....

 

regards, 

florent

 

Hi Florent

the moon has Virtually been over Orion for the last week as well as its been in 80%+ phases, The algorithm will always pick an object better placed as that's the point

Its now cloudy for a couple of days and lets see what happens with the moon out the way and clear from Thursday

Steve

Steve,

Still somewhat confused.

Job 1156 (Rosette) has not been been completed, but the much later 1375 has. 1156 is narrowband and 1375 RGB. According to your note narrowband should be easier to complete as less affected by moon.

Have I completely misunderstood the process?

There is something wrong with old jobs . 

My last submiited jobs , 001434 p14 ic405 ,  RGB ,  is currently processing last week .  it much closer to the moon than orion last week , and older job M42 still stuck . 

I will add also , that job rosette 1156 was already at 33% on 19 october   . So it is clear that old jobs are stuck .

Steve,

Still somewhat confused.

Job 1156 (Rosette) has not been been completed, but the much later 1375 has. 1156 is narrowband and 1375 RGB. According to your note narrowband should be easier to complete as less affected by moon.

Have I completely misunderstood the process?

I think I understand now

Our algorithm is really very good and extremely complex, also the prioritisation works very well, however there is one caveat

EG

if members put 3 different rosettes  in it will choose the best one to image on any given clear night while taking into account the moon phase and relative distance to the object

• OIII & SII will take a higher priority over HA which is why 1375 has already completed these filters
• RGB has a higher priority that HA so if its able it will do RBG over HA
• Luminance will take even higher priority

If it has say been cloudy while the moon was in a larger phase but its now clear while the moon is down our system will then prioritise comets and luminance above all else. This is why at times you may have to wait for HA

I do behind the scenes tweak things occasionality when I need to (that members are unaware of) to finish any jobs that are hanging around due to a run of bad weather but on the whole I leave it to its own devices as

I seem to think when its clear it goes through the data quite quickly and delivers a lot of data, although not always in the order that you "the members" want ?

There is not enough man hours in the day for me to do data acquisition manually on 14 piers and expect to sleep  :)

Steve

I will add also , that job rosette 1156 was already at 33% on 19 october   . So it is clear that old jobs are stuck .

Florent

I am hoping my previous response answers your question, however I will add this

1. the jobs are not stuck and the percentage finished goes up every clear night
2. more goes on behind the scenes than the numbers you see on the queue
3. the queue is an information rough guide to keep you abreast of how things are going, and was only ever put forward as a nicety for members so you could see what data sets were going to be arriving soon. NOT so an automated system that clearly on the whole works very very well be second guessed every few weeks
4. Automated systems work on maths and maths alone so what we believe or even hope it should image is not always what the maths decides and in my experience cold hard math is normally truthful not to mention logical :)
5. I have far deeper access behind the scenes as to how the system is working and what's going on and if you think I don't keep my eye on things like a hawk then you don't know me well (note the Spaghetti nebula as well as the other big job are on pause to help complete the main data sets) this is only one thing of many that I am doing.
6. I am also ensuring that the smaller jobs get finished because of the impending trip to remove the reducer which would render all  existing jobs useless otherwise

Florent - just trust me is what I am saying as I am on it don't worry :)

you plan to remove reducer when ? 

you plan to remove reducer when ? 

 

Now the borders are opening up again we have a trip planned for the end of February, It was supposed to be done in November but France closed the border and omicron etc put that on hold

Steve

oki :)

Steve,

Still somewhat confused.

Job 1156 (Rosette) has not been been completed, but the much later 1375 has. 1156 is narrowband and 1375 RGB. According to your note narrowband should be easier to complete as less affected by moon.

Have I completely misunderstood the process?

I think I understand now

Our algorithm is really very good and extremely complex, also the prioritisation works very well, however there is one caveat

EG

if members put 3 different rosettes  in it will choose the best one to image on any given clear night while taking into account the moon phase and relative distance to the object

• OIII & SII will take a higher priority over HA which is why 1375 has already completed these filters
• RGB has a higher priority that HA so if its able it will do RBG over HA
• Luminance will take even higher priority

If it has say been cloudy while the moon was in a larger phase but its now clear while the moon is down our system will then prioritise comets and luminance above all else. This is why at times you may have to wait for HA

I do behind the scenes tweak things occasionality when I need to (that members are unaware of) to finish any jobs that are hanging around due to a run of bad weather but on the whole I leave it to its own devices as

I seem to think when its clear it goes through the data quite quickly and delivers a lot of data, although not always in the order that you "the members" want ?

There is not enough man hours in the day for me to do data acquisition manually on 14 piers and expect to sleep  :)

Steve

OK. I understand better. I was reading the priorities upside down!

 

 

Steve,

Still somewhat confused.

Job 1156 (Rosette) has not been been completed, but the much later 1375 has. 1156 is narrowband and 1375 RGB. According to your note narrowband should be easier to complete as less affected by moon.

Have I completely misunderstood the process?

I think I understand now

Our algorithm is really very good and extremely complex, also the prioritisation works very well, however there is one caveat

EG

if members put 3 different rosettes  in it will choose the best one to image on any given clear night while taking into account the moon phase and relative distance to the object

• OIII & SII will take a higher priority over HA which is why 1375 has already completed these filters
• RGB has a higher priority that HA so if its able it will do RBG over HA
• Luminance will take even higher priority

If it has say been cloudy while the moon was in a larger phase but its now clear while the moon is down our system will then prioritise comets and luminance above all else. This is why at times you may have to wait for HA

I do behind the scenes tweak things occasionality when I need to (that members are unaware of) to finish any jobs that are hanging around due to a run of bad weather but on the whole I leave it to its own devices as

I seem to think when its clear it goes through the data quite quickly and delivers a lot of data, although not always in the order that you "the members" want ?

There is not enough man hours in the day for me to do data acquisition manually on 14 piers and expect to sleep  :)

Steve

OK. I understand better. I was reading the priorities upside down!

 

 

 

No worries, glad we goth there. I do understand the lack of control can at times seem frustrating and almost illogical in the way it images but the system seems to know what it's doing :)

Its' clear from Thursday again, so should pile through the rest of it well before the trip to Spain at the end of the month