Proposed File(s)
20150416.12 to 20150417.08 hal
Affiliated Mirror
Reason
(August 10th 2015)
Hello DDWG,
I know I have some loose ends to look into this, but it's becoming too outstanding without taking some kind of action. I've also talked this through with some of the folks at BAS, so it shouldn't be too much of a shock.
It seems as though from the period of 20150416.12 to 20150417.08, the Halley radar (hal) rawacf files have a problem with them. The more troubling piece here is that older versions of the RST (2.x I think) appear to not have a problem with these files. However, I've had a problem with trying to process these files here at Virginia Tech with the VTRST 3.5 code.
The long story is that I looked into it a while ago and it appeared as though some kind of memory allocation was being corrupted and causing things to crash. If anyone is interested more, e-mail me directly and I can get back to my notes on when I was working on this a few months ago.
For now, I have moved these from the usual VT archive and backed them up so that I can continue to investigate why RST 2.x processes these files, but VTRST 3.5 does not.
Does anyone else have these issues with these files? If so, maybe we should look to putting them in a separate place on the USask mirror as well.
Cheers,
-Kevin S.
Proposed File(s)
20150416.12 to 20150417.08 hal
Affiliated Mirror
Reason
(August 10th 2015)
Hello DDWG,
I know I have some loose ends to look into this, but it's becoming too outstanding without taking some kind of action. I've also talked this through with some of the folks at BAS, so it shouldn't be too much of a shock.
It seems as though from the period of 20150416.12 to 20150417.08, the Halley radar (hal) rawacf files have a problem with them. The more troubling piece here is that older versions of the RST (2.x I think) appear to not have a problem with these files. However, I've had a problem with trying to process these files here at Virginia Tech with the VTRST 3.5 code.
The long story is that I looked into it a while ago and it appeared as though some kind of memory allocation was being corrupted and causing things to crash. If anyone is interested more, e-mail me directly and I can get back to my notes on when I was working on this a few months ago.
For now, I have moved these from the usual VT archive and backed them up so that I can continue to investigate why RST 2.x processes these files, but VTRST 3.5 does not.
Does anyone else have these issues with these files? If so, maybe we should look to putting them in a separate place on the USask mirror as well.
Cheers,
-Kevin S.