Re: [Emc-developers] Backplot MAX_POINTS

[Greg C]

Haha, thanks Andy.  I'll save this for when others inevitably forget  :-D

-Greg

On Sat, Dec 10, 2022 at 2:41 PM andy pugh  wrote:

> On Sat, 10 Dec 2022 at 19:08, Greg C  wrote:
>
> I wonder if anyone is opposed to adding a 0 and bumping it up 10x?
>
>
> Master is open for such daredevil experimentation :-)
>
> --
> 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 mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Backplot MAX_POINTS

[andy pugh]

On Sat, 10 Dec 2022 at 19:08, Greg C  wrote:

I wonder if anyone is opposed to adding a 0 and bumping it up 10x?


Master is open for such daredevil experimentation :-)

-- 
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

Re: [Emc-developers] Backplot MAX_POINTS

[Greg C]

On Thu, Dec 8, 2022 at 10:39 PM Jon Elson  wrote:

> On 12/8/22 20:12, Greg C wrote:
> > I wonder if anyone has insight to:
> > 1. Why MAX_POINTS was lowered?
> > 2. If I increased this back to 10 or even 100, are there any
> > potential negative side effects (I didn't see anything obvious in the
> brief
> > testing I did)?
> >
> There were complaints that very long G-code files could take
> up to 45 minutes to render, and apparently you could not
> begin running the program until that had completed.
>

Just to make sure we are in alignment, I am talking about the live
plotter.  AFAIK, that's information is populated in real time while running
the program.

I tested this by using eoffsets to deviate from the tool path while the
program is running.  If the information was populated ahead of time,
there's no way my deviations would be plotted properly, which they were.


> Jon


On Thu, Dec 8, 2022 at 9:27 PM Sam Sokolik  wrote:

> Iirc it was just to make the preview more responsive...
>

Interesting.  I bumped it back to the original setting from 2009, and in my
albeit brief testing, I see no appreciable difference other than the tail
of the tool path does not unwind anymore.  There didn't seem to be any
noticeable effects on memory resources either.

I wonder if anyone is opposed to adding a 0 and bumping it up 10x?

>
> On Thu, Dec 8, 2022, 8:16 PM Greg C  wrote:
>
> > Good evening all,
> >
> > Recently on the forum turbostew brought up an issue that I've noticed in
> > the past (in PathPilot) where on large cut files, the backplot starts to
> > turn back to white at the beginning of the previewed cut paths.  Thread
> > <
> >
> https://forum.linuxcnc.org/qtvcp/41566-seems-like-a-buffer-size-limit-on-toolpath-highlighting?start=0#200370
> > >
> >
> > What is actually happening is the max number of points is reached and the
> > oldest points are falling off as the new points are added.  Since the
> > number of MAX_POINTS is defined in emcmodule.cc, this would affect all
> > guis.  emcmodule.cc L1981
> > <
> >
> https://github.com/LinuxCNC/linuxcnc/blob/131761f462ff0194a5403500f03f1f47c5899896/src/emc/usr_intf/axis/extensions/emcmodule.cc#L1981
> > >
> >
> > Back in June of 2009 Jeff Epler lowered this value from 10 to 1,
> > and unfortunately the commit doesn't give any details as to why.  Jeff's
> > Commit
> > <
> >
> https://github.com/LinuxCNC/linuxcnc/commit/13e76953aaa61da0c560418cfbc117436d8c9f38
> > >
> >
> > I wonder if anyone has insight to:
> > 1. Why MAX_POINTS was lowered?
> > 2. If I increased this back to 10 or even 100, are there any
> > potential negative side effects (I didn't see anything obvious in the
> brief
> > testing I did)?
> >
> > Thanks,
> > Greg
> >
> > P.S. the way the backplotter "unwinds" on the beginning of the preview
> > while adding to the current points of the cut path reminds me of the old
> > computer game "Snake".  So I wonder if I increase the length of the
> snake,
> > is there potential for it to "crash" into itself.  🙂
> >
> > ___
> > Emc-developers mailing list
> > Emc-developers@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/emc-developers
> >
>
> ___
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers
>

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

Re: [Emc-developers] Backplot MAX_POINTS

[Sam Sokolik]

Iirc it was just to make the preview more responsive...

On Thu, Dec 8, 2022, 8:16 PM Greg C  wrote:

> Good evening all,
>
> Recently on the forum turbostew brought up an issue that I've noticed in
> the past (in PathPilot) where on large cut files, the backplot starts to
> turn back to white at the beginning of the previewed cut paths.  Thread
> <
> https://forum.linuxcnc.org/qtvcp/41566-seems-like-a-buffer-size-limit-on-toolpath-highlighting?start=0#200370
> >
>
> What is actually happening is the max number of points is reached and the
> oldest points are falling off as the new points are added.  Since the
> number of MAX_POINTS is defined in emcmodule.cc, this would affect all
> guis.  emcmodule.cc L1981
> <
> https://github.com/LinuxCNC/linuxcnc/blob/131761f462ff0194a5403500f03f1f47c5899896/src/emc/usr_intf/axis/extensions/emcmodule.cc#L1981
> >
>
> Back in June of 2009 Jeff Epler lowered this value from 10 to 1,
> and unfortunately the commit doesn't give any details as to why.  Jeff's
> Commit
> <
> https://github.com/LinuxCNC/linuxcnc/commit/13e76953aaa61da0c560418cfbc117436d8c9f38
> >
>
> I wonder if anyone has insight to:
> 1. Why MAX_POINTS was lowered?
> 2. If I increased this back to 10 or even 100, are there any
> potential negative side effects (I didn't see anything obvious in the brief
> testing I did)?
>
> Thanks,
> Greg
>
> P.S. the way the backplotter "unwinds" on the beginning of the preview
> while adding to the current points of the cut path reminds me of the old
> computer game "Snake".  So I wonder if I increase the length of the snake,
> is there potential for it to "crash" into itself.  🙂
>
> ___
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers
>

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

[Emc-developers] Backplot MAX_POINTS

[Greg C]

Good evening all,

Recently on the forum turbostew brought up an issue that I've noticed in
the past (in PathPilot) where on large cut files, the backplot starts to
turn back to white at the beginning of the previewed cut paths.  Thread


What is actually happening is the max number of points is reached and the
oldest points are falling off as the new points are added.  Since the
number of MAX_POINTS is defined in emcmodule.cc, this would affect all
guis.  emcmodule.cc L1981


Back in June of 2009 Jeff Epler lowered this value from 10 to 1,
and unfortunately the commit doesn't give any details as to why.  Jeff's
Commit


I wonder if anyone has insight to:
1. Why MAX_POINTS was lowered?
2. If I increased this back to 10 or even 100, are there any
potential negative side effects (I didn't see anything obvious in the brief
testing I did)?

Thanks,
Greg

P.S. the way the backplotter "unwinds" on the beginning of the preview
while adding to the current points of the cut path reminds me of the old
computer game "Snake".  So I wonder if I increase the length of the snake,
is there potential for it to "crash" into itself.  🙂

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