-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Household ID needs to be integer? #3
Comments
Yes it needs to be integer right now. As of right now you supply the whole data set as We could go from Or we change the way the inputs work and supply inputs seperately. So we dont supply as hid the position of the column in data but the column vector itself. If we would go down this road it would make sense change this for other parameters too. And we would need to specify how the output should look like, since for the implementation as of right now we input the data set and simply return it with changed rows. What do think would be the best option, also regarding possible changes for your JAVA frontend? |
I have a problem with the version 0.2.0 that I hadn't in 0.1.0 related to integer values.
I get: |
@mescudero84 should be fixed now, had a bug when checking the inputs. |
Ok, thank you! |
In my microdata the householdID is 12 digits (maximum).
When I apply record swapping, I get negative housholdIDs back.
Looks like householdID needs to be integer and thus any number > MAXINT (=2147483647) is mapped to a negative number? The maximum householdID I find in the output is exactly 2147483647.
Can this be changed to allow for larger number of digits?
The text was updated successfully, but these errors were encountered: