Commit summary from repository starlink
------------------------------------
(Tim Jenness) smurf: Fix output of padding value
100.0% applications/smurf/libsmf/
(Tim Jenness) smurf: Can not recalculate step time with only one step
100.0% applications/smurf/libsmf/
(Tim Jenness) smurf: If report is true we should report in the recursive call
100.0% applications/smurf/libsmf/
Commits from repository starlink
-----------------------------
commit 611937f88e0020409367a7ca20070f2b9908e772
Author: Tim Jenness <[log in to unmask]>
Date: Sat Oct 9 17:32:57 2010 -1000
smurf: Fix output of padding value
When things go wrong a 64-bit int overflows msgSeti for the padding.
Fix this by using a formatted msgOutf to report the padding with
the proper formatting for a dim_t.
applications/smurf/libsmf/smf_iteratemap.c | 5 ++---
1 files changed, 2 insertions(+), 3 deletions(-)
commit dcbb6015fe4d6437ad799fc0582199568d1da7b1
Author: Tim Jenness <[log in to unmask]>
Date: Sat Oct 9 17:31:11 2010 -1000
smurf: Can not recalculate step time with only one step
Well, you can by using RTS_END and TCS_TAI but it's not very
accurate.
This fixes the cases where a sequence length causes a single step
to be written to a file. First spotted in s8d20100122_00055_0008
which ended up with a NaN step time.
.../smurf/libsmf/smf_fix_metadata_scuba2.c | 36 +++++++++++++----
1 files changed, 27 insertions(+), 9 deletions(-)
commit 05b269203546a31b7647be6926fa7844858aa679
Author: Tim Jenness <[log in to unmask]>
Date: Sat Oct 9 17:03:17 2010 -1000
smurf: If report is true we should report in the recursive call
applications/smurf/libsmf/smf_get_padding.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
|