Why does the lubridate::ymd_hms function add an NA observation when the “silent” argument is set TRUE?












0















Could any one explain why the "silent=T" argument triggers a warning and an NA observation, and tell me how to avoid this?



x <- c("2010-04-14-04-35-59", "20100401120000")

ymd_hms(x, silent=T)

[1] "2010-04-14 04:35:59 UTC" "2010-04-01 12:00:00 UTC" NA                       



Warning message:

1 failed to parse.


R version 3.4.0, lubridate version 1.6.0






r lubridate







share|improve this question




















  • 1





    silent is not an argument of ymd_hms. Do you want ymd_hms(x, quiet = TRUE) ?

    – markus
    Oct 12 '17 at 9:23











  • Ah - sorry - ofcourse - thank you

    – hebbe
    Oct 12 '17 at 9:28


















0















Could any one explain why the "silent=T" argument triggers a warning and an NA observation, and tell me how to avoid this?



x <- c("2010-04-14-04-35-59", "20100401120000")

ymd_hms(x, silent=T)

[1] "2010-04-14 04:35:59 UTC" "2010-04-01 12:00:00 UTC" NA                       



Warning message:

1 failed to parse.


R version 3.4.0, lubridate version 1.6.0






r lubridate







share|improve this question




















  • 1





    silent is not an argument of ymd_hms. Do you want ymd_hms(x, quiet = TRUE) ?

    – markus
    Oct 12 '17 at 9:23











  • Ah - sorry - ofcourse - thank you

    – hebbe
    Oct 12 '17 at 9:28
















0












0








0








Could any one explain why the "silent=T" argument triggers a warning and an NA observation, and tell me how to avoid this?



x <- c("2010-04-14-04-35-59", "20100401120000")

ymd_hms(x, silent=T)

[1] "2010-04-14 04:35:59 UTC" "2010-04-01 12:00:00 UTC" NA                       



Warning message:

1 failed to parse.


R version 3.4.0, lubridate version 1.6.0






r lubridate







share|improve this question
















Could any one explain why the "silent=T" argument triggers a warning and an NA observation, and tell me how to avoid this?



x <- c("2010-04-14-04-35-59", "20100401120000")

ymd_hms(x, silent=T)

[1] "2010-04-14 04:35:59 UTC" "2010-04-01 12:00:00 UTC" NA                       



Warning message:

1 failed to parse.


R version 3.4.0, lubridate version 1.6.0






r lubridate




r lubridate






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Oct 12 '17 at 9:27







hebbe

















asked Oct 12 '17 at 9:11









hebbehebbe

386




386








  • 1





    silent is not an argument of ymd_hms. Do you want ymd_hms(x, quiet = TRUE) ?

    – markus
    Oct 12 '17 at 9:23











  • Ah - sorry - ofcourse - thank you

    – hebbe
    Oct 12 '17 at 9:28
















  • 1





    silent is not an argument of ymd_hms. Do you want ymd_hms(x, quiet = TRUE) ?

    – markus
    Oct 12 '17 at 9:23











  • Ah - sorry - ofcourse - thank you

    – hebbe
    Oct 12 '17 at 9:28










1




1





silent is not an argument of ymd_hms. Do you want ymd_hms(x, quiet = TRUE) ?

– markus
Oct 12 '17 at 9:23





silent is not an argument of ymd_hms. Do you want ymd_hms(x, quiet = TRUE) ?

– markus
Oct 12 '17 at 9:23













Ah - sorry - ofcourse - thank you

– hebbe
Oct 12 '17 at 9:28







Ah - sorry - ofcourse - thank you

– hebbe
Oct 12 '17 at 9:28














2 Answers
2






active

oldest

votes


















1














Here, lubridate tries to evaluate "silent=T" as a date format, the argument for removing message being quiet. 



lubridate::ymd_hms(x, quiet=TRUE)

[1] "2010-04-14 04:35:59 UTC" "2010-04-01 12:00:00 UTC"


This is because you can pass vector inside a lubridate function : 



x <- c("2010-04-14-04-35-59", "20100401120000")

y <- c("2010-04-14-04-35-59", "20100401120000")

z <- c("2010-04-14-04-35-59", "20100401120000")



lubridate::ymd_hms(x, y, z)

[1] "2010-04-14 04:35:59 UTC" "2010-04-01 12:00:00 UTC"

[3] "2010-04-14 04:35:59 UTC" "2010-04-01 12:00:00 UTC"

[5] "2010-04-14 04:35:59 UTC" "2010-04-01 12:00:00 UTC"


So here, with silent=T, you're telling lubridate that silent=T is a vector to parse. Hence the NA.






share|improve this answer































    0














    I faced this issue for cases where the format is different. Please see that all the dates are following the same format. Using parse_date_time() can solve this problem.



    parse_date_time(df$date, c("y/m/d","y/m/d HMS","m/d/y","m/d/y HM"))


    Please be sure that the date format is contained in the list.






    share|improve this answer

























      Your Answer






      StackExchange.ifUsing("editor", function () {
      StackExchange.using("externalEditor", function () {
      StackExchange.using("snippets", function () {
      StackExchange.snippets.init();
      });
      });
      }, "code-snippets");

      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "1"
      };
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function() {
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled) {
      StackExchange.using("snippets", function() {
      createEditor();
      });
      }
      else {
      createEditor();
      }
      });

      function createEditor() {
      StackExchange.prepareEditor({
      heartbeatType: 'answer',
      autoActivateHeartbeat: false,
      convertImagesToLinks: true,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: 10,
      bindNavPrevention: true,
      postfix: "",
      imageUploader: {
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      },
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      });


      }
      });














      draft saved

      draft discarded


















      StackExchange.ready(
      function () {
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f46705695%2fwhy-does-the-lubridateymd-hms-function-add-an-na-observation-when-the-silent%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      2 Answers
      2






      active

      oldest

      votes








      2 Answers
      2






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      1














      Here, lubridate tries to evaluate "silent=T" as a date format, the argument for removing message being quiet. 



      lubridate::ymd_hms(x, quiet=TRUE)
      
[1] "2010-04-14 04:35:59 UTC" "2010-04-01 12:00:00 UTC"


      This is because you can pass vector inside a lubridate function : 



      x <- c("2010-04-14-04-35-59", "20100401120000")
      
y <- c("2010-04-14-04-35-59", "20100401120000")
      
z <- c("2010-04-14-04-35-59", "20100401120000")
      

      
lubridate::ymd_hms(x, y, z)
      
[1] "2010-04-14 04:35:59 UTC" "2010-04-01 12:00:00 UTC"
      
[3] "2010-04-14 04:35:59 UTC" "2010-04-01 12:00:00 UTC"
      
[5] "2010-04-14 04:35:59 UTC" "2010-04-01 12:00:00 UTC"


      So here, with silent=T, you're telling lubridate that silent=T is a vector to parse. Hence the NA.






      share|improve this answer




























        1














        Here, lubridate tries to evaluate "silent=T" as a date format, the argument for removing message being quiet. 



        lubridate::ymd_hms(x, quiet=TRUE)
        
[1] "2010-04-14 04:35:59 UTC" "2010-04-01 12:00:00 UTC"


        This is because you can pass vector inside a lubridate function : 



        x <- c("2010-04-14-04-35-59", "20100401120000")
        
y <- c("2010-04-14-04-35-59", "20100401120000")
        
z <- c("2010-04-14-04-35-59", "20100401120000")
        

        
lubridate::ymd_hms(x, y, z)
        
[1] "2010-04-14 04:35:59 UTC" "2010-04-01 12:00:00 UTC"
        
[3] "2010-04-14 04:35:59 UTC" "2010-04-01 12:00:00 UTC"
        
[5] "2010-04-14 04:35:59 UTC" "2010-04-01 12:00:00 UTC"


        So here, with silent=T, you're telling lubridate that silent=T is a vector to parse. Hence the NA.






        share|improve this answer


























          1












          1








          1







          Here, lubridate tries to evaluate "silent=T" as a date format, the argument for removing message being quiet. 



          lubridate::ymd_hms(x, quiet=TRUE)
          
[1] "2010-04-14 04:35:59 UTC" "2010-04-01 12:00:00 UTC"


          This is because you can pass vector inside a lubridate function : 



          x <- c("2010-04-14-04-35-59", "20100401120000")
          
y <- c("2010-04-14-04-35-59", "20100401120000")
          
z <- c("2010-04-14-04-35-59", "20100401120000")
          

          
lubridate::ymd_hms(x, y, z)
          
[1] "2010-04-14 04:35:59 UTC" "2010-04-01 12:00:00 UTC"
          
[3] "2010-04-14 04:35:59 UTC" "2010-04-01 12:00:00 UTC"
          
[5] "2010-04-14 04:35:59 UTC" "2010-04-01 12:00:00 UTC"


          So here, with silent=T, you're telling lubridate that silent=T is a vector to parse. Hence the NA.






          share|improve this answer













          Here, lubridate tries to evaluate "silent=T" as a date format, the argument for removing message being quiet. 



          lubridate::ymd_hms(x, quiet=TRUE)
          
[1] "2010-04-14 04:35:59 UTC" "2010-04-01 12:00:00 UTC"


          This is because you can pass vector inside a lubridate function : 



          x <- c("2010-04-14-04-35-59", "20100401120000")
          
y <- c("2010-04-14-04-35-59", "20100401120000")
          
z <- c("2010-04-14-04-35-59", "20100401120000")
          

          
lubridate::ymd_hms(x, y, z)
          
[1] "2010-04-14 04:35:59 UTC" "2010-04-01 12:00:00 UTC"
          
[3] "2010-04-14 04:35:59 UTC" "2010-04-01 12:00:00 UTC"
          
[5] "2010-04-14 04:35:59 UTC" "2010-04-01 12:00:00 UTC"


          So here, with silent=T, you're telling lubridate that silent=T is a vector to parse. Hence the NA.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Oct 12 '17 at 9:24









          Colin FAYColin FAY

          2,2231521




          2,2231521

























              0














              I faced this issue for cases where the format is different. Please see that all the dates are following the same format. Using parse_date_time() can solve this problem.



              parse_date_time(df$date, c("y/m/d","y/m/d HMS","m/d/y","m/d/y HM"))


              Please be sure that the date format is contained in the list.






              share|improve this answer






























                0














                I faced this issue for cases where the format is different. Please see that all the dates are following the same format. Using parse_date_time() can solve this problem.



                parse_date_time(df$date, c("y/m/d","y/m/d HMS","m/d/y","m/d/y HM"))


                Please be sure that the date format is contained in the list.






                share|improve this answer




























                  0












                  0








                  0







                  I faced this issue for cases where the format is different. Please see that all the dates are following the same format. Using parse_date_time() can solve this problem.



                  parse_date_time(df$date, c("y/m/d","y/m/d HMS","m/d/y","m/d/y HM"))


                  Please be sure that the date format is contained in the list.






                  share|improve this answer















                  I faced this issue for cases where the format is different. Please see that all the dates are following the same format. Using parse_date_time() can solve this problem.



                  parse_date_time(df$date, c("y/m/d","y/m/d HMS","m/d/y","m/d/y HM"))


                  Please be sure that the date format is contained in the list.







                  share|improve this answer














                  share|improve this answer



                  share|improve this answer








                  edited Nov 23 '18 at 7:00









                  Marcus Campbell

                  2,08331228




                  2,08331228










                  answered Nov 23 '18 at 6:35









                  Praveen KumarPraveen Kumar

                  11




                  11






























                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to Stack Overflow!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid …



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f46705695%2fwhy-does-the-lubridateymd-hms-function-add-an-na-observation-when-the-silent%23new-answer', 'question_page');
                      }
                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      -

                      這個網誌中的熱門文章

                      Xamarin.form Move up view when keyboard appear

                      圖片
                      .everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box; } 0 I'm trying to build a Chat app UI, the idea of the Layout was pretty simple: When the input bar is focused, keyboard show up and "push" up the chat bar, as it's a grid, the ListView will resize to fit the screen: I update the input bar's margin to "push" it up: NSValue result = (NSValue)args.Notification.UserInfo.ObjectForKey(new NSString(UIKeyboard.FrameEndUserInfoKey)); CGSize keyboardSize = result.RectangleFValue.Size; if (Element != null){ Element.Margin = new Thickness(0, 0, 0,keyboardSize.Height); //push the entry up to keyboard height when keyboard is activated } And this is ...
                      閱讀完整內容

                      Post-Redirect-Get with Spring WebFlux and Thymeleaf

                      圖片
                      .everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box; } 2 Can someone explain to me how to implement the post-redirect-get pattern in Spring WebFlux and Thymeleaf? What subscribes on the database save method? @GetMapping("/register") public String showRegisterForm(Model model) { model.addAttribute("user", new User()); return "register"; } @PostMapping public String processRegisterForm(@Valid User user, BindingResult bindingResult) { if (bindingResult.hasErrors()) { return "register"; } else { userRepository.save(user); //what subscribes on this? //how to redirect on e.g. "/login"? ...
                      閱讀完整內容

                      Anylogic : not able to use stopDelay()

                      圖片
                      -2 I am building a railway station model. I want a train to depart when I click a button. I want to call stopDelay() for that but I am not sure how to do that and from which place. anylogic share | improve this question asked Nov 23 '18 at 10:12 Anupam Singh Anupam Singh 1 Hi Anupam, welcome to SOF. Please check how to ask good questions, see link below. Your question is...
                      閱讀完整內容