Document and test input_dtype
and output_dtype
policy
#350
Labels
discussion required
Some discussion necessary to decide how to address this issue
documentation
Improvements or additions to documentation
tests
Pertaining to SCICO tests
We should decide what
input_dtype
andoutput_dtype
mean, then document it.Proposed
input_dtype
andoutput_dtype
policy:Operator
s must haveinput_dtype
andoutput_dtype
propertiessnp.float32
,snp.float64
,snp.complex64
Operator
, we should callsnp.dtype(input_dtype)
to make sure it is a dtype and not a typeprint(snp.float32)
andprint(snp.dtype(snp.float32))
, second has nice replOperator
H
,H(x)
should throw an error ifx.dtype
is notinput_dtype
Operator
s should be written so thatH(x).dtype
isH.output_dtype
; this will not be checked and runtime, but should be testedOperator
s should attempt to automatically deduceinput_dtype
andoutput_dtype
from other arguments and throw an error if the user requests aninput_dtype
oroutput_dtype
that is not realizableThis policy should be described in the docs and implemented in the code.
Related: #165 #234
The text was updated successfully, but these errors were encountered: