Previously, dtype in the archive could only be a single value specifying the dtype for the solution, objective, and measures all at once. Now, it is allowed to be a dict specifying separate dtypes for each of these, e.g.,
This PR is a followup to #470 which allowed expressing the different dtypes present in the archive.
Emitters used the dtype of their archive, e.g., archive.dtype. Now, they choose a specific field's dtype to use. The emitters implemented thus far all choose archive.dtypes["solution"], i.e., they have the same dtype as the solution.
Description
Previously, dtype in the archive could only be a single value specifying the dtype for the solution, objective, and measures all at once. Now, it is allowed to be a dict specifying separate dtypes for each of these, e.g.,
Comments:
archive.dtype
. Now, they choose a specific field's dtype to use. The emitters implemented thus far all choosearchive.dtypes["solution"]
, i.e., they have the same dtype as the solution.TODO
Status
yapf
pytest
pylint
HISTORY.md