As far as I know, nobody yet includes uncertainties in Q. However a few in the community are starting to think about it and it is not unreasonable to expect that, sometime soon, files may start to exist. Thus we should probably try to provide an object which can deal with uncertainties on all quantities we do math with?
It seems that the data object itself does in fact treat Q like any other quantity that can have uncertainties for when we start actually providing those. However, it seems that currently the resolution width is being automatically added as the uncertainty in Q which it is not. It is however a critical quantity in its own right and needs its on space. It also needs to be treated in a very special way. Longer term, figuring out how to propagate the resolution function through operations, if possible, needs to be figured out and then implemented. NOTE: I'm not sure that the math for such has been worked out by anybody.
As far as I know, nobody yet includes uncertainties in Q. However a few in the community are starting to think about it and it is not unreasonable to expect that, sometime soon, files may start to exist. Thus we should probably try to provide an object which can deal with uncertainties on all quantities we do math with?
It seems that the data object itself does in fact treat Q like any other quantity that can have uncertainties for when we start actually providing those. However, it seems that currently the resolution width is being automatically added as the uncertainty in Q which it is not. It is however a critical quantity in its own right and needs its on space. It also needs to be treated in a very special way. Longer term, figuring out how to propagate the resolution function through operations, if possible, needs to be figured out and then implemented. NOTE: I'm not sure that the math for such has been worked out by anybody.