-
Notifications
You must be signed in to change notification settings - Fork 61
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[GSProcessing] Fix support for large integer values for noop transfom…
…ation (#707) For now we also parse all numerical CSV values as float64. In the future we'll allow the use the option to choose, defaulting at float32. *Issue #, if available:* Fixes #706 *Description of changes:* * For CSV numerical feature input always parse as float64. We plan to allow this to be user-defined in the future. * For CSV regression label input always parse as float64. We plan to allow this to be user-defined in the future. * For Parquet numerical feature input for noop transformation, use the input's data type, to avoid precision loss by converting to float32. * For CSV numerical input for noop transformation (which is parsed as string), output to float64. *How this was tested*: * Added relevant unit test * Tested on generated graph dataset with integer features with values up to 80M, results shown below <img width="1094" alt="image" src="https://github.com/awslabs/graphstorm/assets/9048995/772dc549-fd09-416c-bf73-71fbf11e634b"> By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
- Loading branch information
Showing
3 changed files
with
43 additions
and
19 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters