Actions
Bug #205
closedsubStack does not copy all stack particle fields
Start date:
03/13/2010
Due date:
% Done:
100%
Estimated time:
Affected Version:
Show in known bugs:
Workaround:
Description
subStack does not copy all stack particle fields. When creating a substack, you may want to keep the kurtosis information.
Updated by Neil Voss about 14 years ago
- Status changed from Assigned to In Code Review
- Assignee changed from Neil Voss to Amber Herold
- % Done changed from 0 to 100
Fixed in r13173.
Test by creating a substack and comfirming that all fields are transferred in ApStackParticlesData.
Updated by Amber Herold about 14 years ago
- Status changed from In Code Review to In Test
Updated by Amber Herold about 14 years ago
- Assignee changed from Amber Herold to Pick-Wei Lau
Updated by Neil Voss almost 14 years ago
- Target version set to Appion/Leginon 2.0.0
Updated by Amber Herold almost 14 years ago
- Assignee changed from Pick-Wei Lau to Anke Mulder
Updated by Anke Mulder almost 14 years ago
- Assignee changed from Anke Mulder to Amber Herold
Not sure. I made a substack, and ApStackParticlesData contains info for the first 6 columns, but none of the kurtosis, mean, stdev information was copied....
Updated by Neil Voss almost 14 years ago
- Assignee changed from Amber Herold to Anke Mulder
Updated by Neil Voss almost 14 years ago
- Status changed from In Test to Closed
- Assignee deleted (
Anke Mulder)
It would only work if the original stack had the kurtosis information, which I think in your case it did not. Looking at Bridget's it appeared that it worked correctly. Closing the bug.
Actions