Re: DConf 2020 Early-Bird Registration & Submission Deadlines
On 1/27/2020 8:16 AM, Murilo wrote: Wait, will you notify the submission authors before or after the deadline? If my submission is accepted, will I need to pay for the registration? If your talk is accepted and you've already bought a ticket, we'll refund it.
Re: D For Data Science: Calling R from D
On Monday, 27 January 2020 at 14:20:20 UTC, Adam D. Ruppe wrote: On Monday, 27 January 2020 at 14:16:47 UTC, Mike Parker wrote: https://dlang.org/blog/2020/01/27/d-for-data-science-calling-r-from-d/ "D [...] interoperability with C (in many cases as simple as adding an #include directive to import a C header file), " like it is simple... but it isn't a #include directive unless you use third party things (that have their own issues). Minor thing but can be misleading to newcomers. Good catch. I intended to link to both dpp and dstep but I forgot to do it.
Re: D For Data Science: Calling R from D
On Monday, 27 January 2020 at 14:55:37 UTC, jmh530 wrote: On Monday, 27 January 2020 at 14:16:47 UTC, Mike Parker wrote: You've seen Lance Bachmeier posting in the forums under the bachmeier handle. He's put together a post for the D Blog showing how to integrate R into a D program. The Blog: https://dlang.org/blog/2020/01/27/d-for-data-science-calling-r-from-d/ Reddit: https://www.reddit.com/r/programming/comments/euobu1/d_for_data_science_calling_r_from_d/ It's also on Hacker News. If it isn't on the front page, just search for "D for Data Science". Please don't post a direct link if you find it on there, not until after it's been on there a few days. https://news.ycombinator.com/ Great piece. Glad to see it. One point that is confusing is below: "There are two ways to execute R code from a D program. evalR executes a string in R and prints the output to the screen, while evalRQ does the same thing but suppresses the output. evalRQ also accepts an array of strings that are executed sequentially." So evalR normally prints the output to the screen, but evalRQ does not unless you specify it with a print statement. However, in Example 4 later have an array of strings with a print statement at the end but it says that it won't print from it. So does Example 4 print or not? Maybe distinguish between suppress in D and print with R a little more clearly? In addition, the embedr documentation could probably be more clear on the difference between evalR and evalRQ using some of this text. Thanks for catching that. I must have messed that up during editing. This is incorrect: "evalR executes a string in R and prints the output to the screen". evalR executes a string in R and then returns the R output to D as an Robj struct. The comment on Example 4 is also wrong. I'll have to think about the best way to word things and ask Mike to make the change.
Re: DConf 2020 Early-Bird Registration & Submission Deadlines
On Monday, 27 January 2020 at 17:49:05 UTC, Steven Schveighoffer wrote: Past conferences you did not have to pay for the conference if you are giving a talk. I think you can hold off registering until you are notified and still get the early bird rate (if you are not chosen), since the date you are notified is the same as the last day of early bird registration. -Steve Thanks.
Re: DConf 2020 Early-Bird Registration & Submission Deadlines
On 1/27/20 11:16 AM, Murilo wrote: On Monday, 27 January 2020 at 12:00:32 UTC, Mike Parker wrote: For those of you intending to make any submissions, that is also the date we'll notify submission authors of their submission status. The submission deadline is April 12 AOE. Wait, will you notify the submission authors before or after the deadline? If my submission is accepted, will I need to pay for the registration? Past conferences you did not have to pay for the conference if you are giving a talk. I think you can hold off registering until you are notified and still get the early bird rate (if you are not chosen), since the date you are notified is the same as the last day of early bird registration. -Steve
Re: DIP Reviews: Discussion vs. Feedback
On Sunday, 26 January 2020 at 09:01:03 UTC, Mike Parker wrote: I'm making a change to the way we solicit feedback during DIP review rounds. The goal is to separate explicit feedback from discussion. Discussion is vital to the process, but it also makes it difficult to find the actionable feedback buried in the 20+ pages that some DIP reviews generate (particularly Walter's). So henceforward, we're going with two threads per review round: one for discussion and one for feedback (critique). It's all laid out in this blog post: https://dlang.org/blog/2020/01/26/dip-reviews-discussion-vs-feedback/ Also on reddit: https://www.reddit.com/r/d_language/comments/eu4fi8/dip_reviews_discussion_vs_feedback/ I think this new policy wants some further pondering. In the feedback theard, if the DIP author replies and the reply indicates that he/she has missed the point of the review, we have a problem. The reviewer cannot answer to the author in the feedback theard, so it has to be done on the discussion theard. With high likelihood, the author will miss the reply on that another theard, and the misunderstanding remains in effect. I think you should let a reviewer to answer to the author in the feedback theard, when the intention is clarify the review. Replying just to disagree with the author, or to comment other reviews still belongs to the discussion thears. That's the minimal fix. However, I suspect there is an alternative arragement, which if as follows: The manager will still create only one feedback theard, where peaple can freely about the DIP and all the reviews given. But to provide a real review, the reviewer will open a new theard and drop a link to to it in the general theard. In the personal review theard, only the reviewer, the author and the DIP manager can talk, and the rules are the same as in the "feedback" theard in the "minimal fix" I described above. To force people to give reviews instead of just bikeshedding in the general theard, there could be a rule that only those who have left a review can participate in the general theard. After the review, the DIP manager will only check the reviews for the review summary. I think this would increase the quality of the reviews, as each reviewer can talk with the author without having the concurrent conversations to drown each other. Thanks for the blog post!
Re: DConf 2020 Early-Bird Registration & Submission Deadlines
On Monday, 27 January 2020 at 12:00:32 UTC, Mike Parker wrote: For those of you intending to make any submissions, that is also the date we'll notify submission authors of their submission status. The submission deadline is April 12 AOE. Wait, will you notify the submission authors before or after the deadline? If my submission is accepted, will I need to pay for the registration?
Re: D For Data Science: Calling R from D
On Monday, 27 January 2020 at 14:16:47 UTC, Mike Parker wrote: You've seen Lance Bachmeier posting in the forums under the bachmeier handle. He's put together a post for the D Blog showing how to integrate R into a D program. The Blog: https://dlang.org/blog/2020/01/27/d-for-data-science-calling-r-from-d/ Reddit: https://www.reddit.com/r/programming/comments/euobu1/d_for_data_science_calling_r_from_d/ It's also on Hacker News. If it isn't on the front page, just search for "D for Data Science". Please don't post a direct link if you find it on there, not until after it's been on there a few days. https://news.ycombinator.com/ Great piece. Glad to see it. One point that is confusing is below: "There are two ways to execute R code from a D program. evalR executes a string in R and prints the output to the screen, while evalRQ does the same thing but suppresses the output. evalRQ also accepts an array of strings that are executed sequentially." So evalR normally prints the output to the screen, but evalRQ does not unless you specify it with a print statement. However, in Example 4 later have an array of strings with a print statement at the end but it says that it won't print from it. So does Example 4 print or not? Maybe distinguish between suppress in D and print with R a little more clearly? In addition, the embedr documentation could probably be more clear on the difference between evalR and evalRQ using some of this text.
Re: D For Data Science: Calling R from D
On Monday, 27 January 2020 at 14:20:20 UTC, Adam D. Ruppe wrote: On Monday, 27 January 2020 at 14:16:47 UTC, Mike Parker wrote: https://dlang.org/blog/2020/01/27/d-for-data-science-calling-r-from-d/ "D [...] interoperability with C (in many cases as simple as adding an #include directive to import a C header file), " like it is simple... but it isn't a #include directive unless you use third party things (that have their own issues). Minor thing but can be misleading to newcomers. Good point. I've added a mention of dpp and a link to the Project Highlight on the blog.
Re: DConf 2020 Early-Bird Registration & Submission Deadlines
On Monday, 27 January 2020 at 13:30:20 UTC, Rory McGuire wrote: There is a typo at: *while enhanching the D ecosystem * R Thanks, Rory!
Re: D For Data Science: Calling R from D
On Monday, 27 January 2020 at 14:16:47 UTC, Mike Parker wrote: https://dlang.org/blog/2020/01/27/d-for-data-science-calling-r-from-d/ "D [...] interoperability with C (in many cases as simple as adding an #include directive to import a C header file), " like it is simple... but it isn't a #include directive unless you use third party things (that have their own issues). Minor thing but can be misleading to newcomers.
D For Data Science: Calling R from D
You've seen Lance Bachmeier posting in the forums under the bachmeier handle. He's put together a post for the D Blog showing how to integrate R into a D program. The Blog: https://dlang.org/blog/2020/01/27/d-for-data-science-calling-r-from-d/ Reddit: https://www.reddit.com/r/programming/comments/euobu1/d_for_data_science_calling_r_from_d/ It's also on Hacker News. If it isn't on the front page, just search for "D for Data Science". Please don't post a direct link if you find it on there, not until after it's been on there a few days. https://news.ycombinator.com/
Re: DConf 2020 Early-Bird Registration & Submission Deadlines
On Mon, Jan 27, 2020 at 2:05 PM Mike Parker via Digitalmars-d-announce < digitalmars-d-announce@puremagic.com> wrote: > [snip] > I'll open registration through PayPal once the official > announcement goes out on the blog and social media. Both > registration options will be available at dconf.org. > [snip] Hi Mike, There is a typo at: *while enhanching the D ecosystem * R
DConf 2020 Early-Bird Registration & Submission Deadlines
I'm currently planning to officially launch early-bird registration for DConf 2020 in early February, hopefully in tandem with news that we have confirmed our invited keynote speaker. Consider this announcement a "soft launch". Those of you eager to get your registrations squared away can do so right now through our Flipcause registration form: https://www.flipcause.com/secure/cause_pdetails/NzQ0NzA= I'll open registration through PayPal once the official announcement goes out on the blog and social media. Both registration options will be available at dconf.org. Once again, the regular registration rate will be $400 USD + 20% VAT, for a total of $480. The early-bird registration is a 15% discount: $340 + 20% VAT for a total of $408 (£312.15 at the January HMRC exchange rate, which may change in February). Early-bird registration is available until April 19 AOE. For those of you intending to make any submissions, that is also the date we'll notify submission authors of their submission status. The submission deadline is April 12 AOE.
