-
Notifications
You must be signed in to change notification settings - Fork 6
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
Parse_date Time Zone Linking Issue #16
Comments
I had a similar problem, it seemed to be because the date column in the metadata.csv file had been formatted to a slash version e.g. 07/07/2020. You need to reformat those cells into the write format, e.g. 2020-07-07. |
Actually this still doesnt seem to work for me, if you figured out the answer please let me know! |
This is an issue that started happening with some update in either R or some of the packages used by rethomics. You need to make sure:
|
Thanks very much for the quick reply @antorjim, your solution helped me a lot! |
Hi @qgeissmann - I reckon this should do it:
|
Should be on its way to CRAN. Hopefully, the patch solves the main issue |
Hi Quentin, I am afraid this either never made it to CRAN or it was not fixed properly because we still experience the bug whenever date is not a character
If this returns |
thanks for picking that up. I will try to have a look ASAP... Do you manage to get it working with the github version of the package?
|
Just tried. Yes, it does work fine with the github version. |
ok. great. I just never sent the confirmation form from CRAN I think. just did that now. That could take a few days to review the package etc, but hopefully should get in soon. Thanks for the reminder! |
|
Hello
So I was reading through the rethomics documentation and playing with the toy data but was unable to link the metadata and data files because of a failure related to parse_date:
`> metadata <- link_ethoscope_metadata(metadata,
Error in parse_date(date, tz = "UTC") : Unexpected type for x`
Is there any way to resolve the tz issue?
Thank you very much in advance!
The text was updated successfully, but these errors were encountered: