[
https://issues.apache.org/jira/browse/MAHOUT-959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13193462#comment-13193462
]
Rares Vernica commented on MAHOUT-959:
--------------------------------------
bq. The vectors are most certainly read back as they are written.
I fully understand this. I actually state this in the first sentence of the
issue description.
My point was, that after VectorWritable reads some floats it might as well
write them back as floats. I understand that they are used as doubles anyway,
but what is the point of doubling the required storage space (by default) if
they had single precision to begin with. It seemed as an easy fix, but now I
see that it is not as straightforward as I thought.
It seemed strange that you have the possibility to write as float, they are
read correctly as float, but what you read as float ends up written as double.
> VectorWritable does not preserve the laxPrecision flag
> ------------------------------------------------------
>
> Key: MAHOUT-959
> URL: https://issues.apache.org/jira/browse/MAHOUT-959
> Project: Mahout
> Issue Type: Bug
> Components: Math
> Affects Versions: 0.6
> Reporter: Rares Vernica
> Assignee: Sean Owen
> Attachments: MAHOUT-959.patch, VerctorWritable-laxPrecicison.patch
>
>
> When reading a vector, VectorWritable uses the laxPrecision flag to read with
> the right precision, but it does not preserve the flag in case the vector is
> written back.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
