[Issues] Target Processor concludes ReadNoise is not uptodate...

[W.J. Vriend]

Hello Hans,

You are right. Not only dependencies_new but also dependencies_obsolete 
should be cleared in the after_uptodate_object method of ReadNoise. 
Please fix this bug and commit it to CVS.

Willem-Jan Vriend.


Hans Vaith wrote:
> Dear All,
>
> I get an unexpected behavior when trying to create a BiasFrame using the 
> TargetProcessor. The ReadNoise does already exist, yet the on-the-fly 
> processing concludes that ReadNoise is not up to date. (I could say 'fine' 
> here, but the remake of the ReadNoise ends in quality=2 and the processing 
> stops with an error, so I would really like the Target Processor to accept my 
> already existing ReadNoise objects)
>
> My guess is that the method after_uptodate_object()  in ReadNoise.py needs to 
> clear the list 'dependencies_obsolete', but it's only a guess, so I am not 
> committing anything to the CVS repository.
>
> Appended is the respective snippet from the log file.
>
> Thanks,
> Hans
>
> 18:00:27 - OnTheFly_get 'ReadNoise' for date='2004-10-02 20:57:42.00' 
> chip='ccd54' filter='' object_id='None' template='None' rec=1 cal=1/99
> 18:00:27 - get_recursive BiasFrame.ReadNoise
> 18:00:27 - found ReadNoise with object_id='24F78B6705BC650BE040B782974A7A95'
> 18:00:27 - ReadNoise (id='24F78B6705BC650BE040B782974A7A95') uptodate for 
> 2004-10-02 20:57:42.00? (rec 1 cal 1/99)
> 18:00:27 - uptodate_recursive BiasFrame.ReadNoise
> 18:00:27 - New RawBiasFrames for ReadNoise do not make it out of date !
> 18:00:27 - Dependencies obsolete of ReadNoise: count=2
> 18:00:27 -  -> ReadNoise is NOT uptodate for date 2004-10-02 20:57:42.00, 
> value 5 {5: 2}
> 18:00:27 - ReadNoise exists, but is not up to date; making new
>
> _______________________________________________
> Issues mailing list
> Issues at astro-wise.org
> http://listman.astro-wise.org/mailman/listinfo/issues
>