Some code [Software]
❝ So you are an advanced RUser!
I'd say that I am at the basement of being an advanced user. Must credit PAGIN (population approach group in India) for introducing me to R and R studio a couple of years back. Its been a good learning curve thereafter.
❝ Welcome. Didn’t know it until yesterday either.
❝ ❝ […] I believed ISO8601 was majorly the standard time format
❝
❝ In many countries. In Austria it is not just a norm but legally binding. Rarely used in daily life.
Interesting...
❝ I was curious myself. My latest code:....
❝ Which gave on my machine:
❝
❝ location local.datetime offset UTC.datetime loc.SAS.datetime UTC.SAS.datetime
❝ Europe/Vienna 2019-03-22 18:32:57 CET +1:00 2019-03-22 17:32:57 UTC 22Mar19:18:32:57 22Mar19:17:32:57
❝ US/Eastern 2019-03-22 13:32:57 EDT -4:00 2019-03-22 17:32:57 UTC 22Mar19:13:32:57 22Mar19:17:32:57
❝ Asia/Kolkata 2019-03-22 23:02:57 IST +5:30 2019-03-22 17:32:57 UTC 22Mar19:23:02:57 22Mar19:17:32:57
❝ Pacific/Auckland 2019-03-23 06:32:57 NZDT +13:00 2019-03-22 17:32:57 UTC 23Mar19:06:32:57 22Mar19:17:32:57
WOW, this looks much better, however I guess while we represent in CDISC it has to be in the form of YYYY-MM-DD for the .XPT. I find myself complicating over this now :( .
More details to this point can be availed by downloading the CDISC Implementation guide 3.3, section 4.4. P.S: requires a mandate registration for viewing/download.
You can download/view the details from HERE
❝ Note the different local times: Poughkeepsie changed EST ↑ EDT on March 10th, Austria will change CET ↑ CEST on March 31th, and New Zealand will change NZDT ↓ NZT on April 7th.
❝ See this funny story.
Interesting read. Little did I know about it. Thank you for bringing it up.
Additionally, while I am fully trying to understand the datasets structure for submission, my ship hit an iceberg this morning.
Under the module structure for submission for datasets as a part of the dossier, as defined by CDISC for USFDA, it requires the SAS programs for ADAM datasets to be given as note file documents.
You can get the module structure from HERE
This looks clearly like CDISC recommends SAS for datasets (which is like a monopoly and it kinda brings us back to point one from where we started this thread :( ).
Thanks and regards
-Dr Anonymous
(WhiteCoatWriter)
Thanks and Regards
Dr Anonymous
(WhiteCoatWriter)
Complete thread:
- CDISC datasets or R. Acceptable ?? WhiteCoatWriter 2019-03-21 07:13 [Software]
- CDISC datasets from R. Why not? Helmut 2019-03-21 10:47
- CDISC datasets from R. Why not? WhiteCoatWriter 2019-03-21 12:13
- CDISC datasets from R. Why not? Helmut 2019-03-21 16:43
- CDISC datasets from R. Why not? WhiteCoatWriter 2019-03-22 06:56
- Some code Helmut 2019-03-22 16:58
- Some codeWhiteCoatWriter 2019-03-24 07:59
- SAS only? Helmut 2019-03-24 12:34
- SAS only? WhiteCoatWriter 2019-03-25 09:39
- Confusing… Helmut 2019-03-25 13:44
- Confusing… WhiteCoatWriter 2019-03-27 06:55
- Confusing… Helmut 2019-03-25 13:44
- SAS only? WhiteCoatWriter 2019-03-25 09:39
- SAS only? Helmut 2019-03-24 12:34
- Some codeWhiteCoatWriter 2019-03-24 07:59
- Some code Helmut 2019-03-22 16:58
- CDISC datasets from R. Why not? WhiteCoatWriter 2019-03-22 06:56
- CDISC datasets from R. Why not? Helmut 2019-03-21 16:43
- CDISC datasets from R. Why not? WhiteCoatWriter 2019-03-21 12:13
- CDISC datasets from R. Why not? Helmut 2019-03-21 10:47