Re: [Emc-developers] [Emc-users] April 2023 LinuxCNC meeting at Tormach headquarters

2023-03-16 Thread Jon Elson
Would anyone who plans to attend please let me know, so I 
can get a total of attendees and inform Tormach how big the 
horde is going to be?


Thanks,

Jon


___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers


Re: [Emc-developers] [Emc-users] April 2023 LinuxCNC meeting at Tormach headquarters

2023-03-16 Thread Jon Elson

On 3/7/23 11:10, Jon Elson wrote:

On 1/18/23 18:29, Jon Elson wrote:
Daniel Rogge of Tormach has mentioned that he is trying 
to set up a meeting in April with Robert Ellenberg, John 
Morris and Alex Rossler over a weekend.  Does anybody 
have a specific date they would prefer or can't attend?  
We could possibly set up a meeting that partly overlaps 
the one with the above people. 


I FINALLY have a DATE!  Tormach is having a meeting with 
the above mentioned developers from April 24 - 28.  Daniel 
suggests we could have a LinuxCNC meeting from April 22-23 
(over the weekend) and then maybe stay just a bit to meet 
with those others.  Sorry it took so long to find out what 
the dates were.


Would anyone who plans to attend please let me know, so I 
can get a total of attendees and inform Tormach how big the 
horde is going to be?


Thanks,

Jon



___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers


Re: [Emc-developers] For 2.10: Suggesting chatGPT checks of our documentation

2023-03-16 Thread Steffen Möller


> Gesendet: Donnerstag, 16. März 2023 um 14:13 Uhr
> Von: "andy pugh" 
> An: "EMC developers" 
> Betreff: Re: [Emc-developers] For 2.10: Suggesting chatGPT checks of our 
> documentation
>
> On Thu, 16 Mar 2023 at 12:10, Steffen Möller  wrote:
> 
> > Hello,
> >
> > I am admittedly still impressed of the linguistic skills of chatGPT
> >
> 
> It's worth considering what ChatGPT does, which is to a large extent just
> choosing the most likely word to continue the sentence.
> In many ways this is just a generic critique that could be relevant to
> almost anything, with some keywords swapped.

So when our chatty friend encounters a text that is not continuous wrt the 
sentences it already knows, like the references to the jitter and the 
descriptions of limitations, then it will point out that this needs some form 
of deeper embedding the text to cater for a fluent read. This is all I want, 
really, for now that is. I also expect that ChatGPT points me to redundancies 
or that it proposes some reordering, but I have not seen this, yet.

There is a side-thought on this. I want our documentation "understood" (are 
those quotes still needed?) by a linguistically skilled robot. That robot could 
then help our new users to set their mill up and (e.g. by integrating the forum 
and I also hope for more YouTube transcripts) also help with error recovery. 

>  Interesting examples:
> https://economistwritingeveryday.com/2023/01/21/chatgpt-cites-economics-papers-that-do-not-exist/

Yes, it is a complete utter failure on provenance, i.e. the introspection on 
where a particular information was found/derived from. But that will come.

Best,
Steffen


___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers


Re: [Emc-developers] For 2.10: Suggesting chatGPT checks of our documentation

2023-03-16 Thread andy pugh
On Thu, 16 Mar 2023 at 12:10, Steffen Möller  wrote:

> Hello,
>
> I am admittedly still impressed of the linguistic skills of chatGPT
>

It's worth considering what ChatGPT does, which is to a large extent just
choosing the most likely word to continue the sentence.
In many ways this is just a generic critique that could be relevant to
almost anything, with some keywords swapped.

 Interesting examples:
https://economistwritingeveryday.com/2023/01/21/chatgpt-cites-economics-papers-that-do-not-exist/

-- 
atp
"A motorcycle is a bicycle with a pandemonium attachment and is designed
for the especial use of mechanical geniuses, daredevils and lunatics."
— George Fitch, Atlanta Constitution Newspaper, 1912

___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers


[Emc-developers] For 2.10: Suggesting chatGPT checks of our documentation

2023-03-16 Thread Steffen Möller
Hello,

I am admittedly still impressed of the linguistic skills of chatGPT. Also, its 
translations seem superior to what Google Translate or DeepL is offering. What 
I have toyed around with is to have chatGPT comment on our documentation. It 
always praises what we have, that is the boring part. But when asking for 
possible improvements, then it goes for 
http://linuxcnc.org/docs/2.9/html/install/latency-test.html like:

"Overall, the documentation provides a clear and comprehensive explanation of 
latency and its importance in LinuxCNC. The instructions for running the 
latency test and interpreting the results are also detailed and easy to follow.

However, there are a few areas that could be improved:

The introduction could benefit from a brief overview of what LinuxCNC is and 
how it works, as this would help newcomers to understand the context of the 
latency test.

The section on the disadvantages of software step pulses could be expanded upon 
to give more detail on why they are limited in terms of maximum step rate and 
pulse jitter.

The instructions for running latency-plot and latency-histogram could be 
expanded upon to provide more detail on how to interpret the output.

Including some troubleshooting tips or common issues that may arise during the 
latency test would be helpful for users who encounter problems.

Overall, the documentation is of good quality and provides useful information 
for novice LinuxCNC users."

My comments on this:

* We do not want to give an overview but a reference to where to find that 
overview could be nice, especially since it is likely that the page was found 
via Google, so the reader may not have the context.
* Introduction is short as it is all explained elsewhere in the documentation, 
but references on why something is limited and what the effect of a jitter is, 
would likely boost the confidence of our readers ("thought so").
* We have a problem with decent captions throughout the documentation.

Best,
Steffen






___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers