Solved search for gcodes

[nikscha]

Hi all,
small rant about the search in the new wiki:
I really dislike how when I search for a gcode on the wiki search, there's often other articles displayed before it. Say I forgot the gcode (or parameters) for setting motor current, and I search for "set motor current", then the right entry only shows up on the 3rd spot: (meaning I can't just press enter to open it)

I wish there was a dedicated search for gcodes only.

Also: The search engine can't deal with typos at all, and every single one of the words in the query has to match. How is this better than just using ctrl+f?

I really like the new wiki, but please overhaul the search

[deckingman]

@nikscha I find this useful for quickly finding gcodes. https://docs.duet3d.com/User_manual/Reference/Gcodes_by_function. (Setting motor currents comes under "Motion").

The problem with searching on a text string is the same as not knowing the gcode number you want. Personally, I think it does a pretty good job because in your example, someone might want to set the base motor current (M906), someone else might want to set the standstill motor current reduction (M917) and someone else might want to know the command for setting the motor current as a percentage of normal current (M913). Even if the search result was limited to G (or M) codes, there are still 3 different "answers" for users who not might not know the exact terminology so only enter "motor current".

Essentially, specific answers can only be given to specific questions.

[nikscha]

@deckingman Thank you for the link, that's indeed helpful.

But I disgree with you on this:

@deckingman said in search for gcodes:

The problem with searching on a text string is the same as not knowing the gcode number you want.

I know exactly what gcode I'm looking for, I just don't remember the number (Personally I just have a hard time with that). So for me it would be easier if I could just type the name of the command instad.

And it doesn't excuse the issue with typos. I (non-native speaker) sometimes misspell english words, and it would be nice if the search engine would be a bit more forgiving.

[oliof]

@nikscha if you search for "gcode set motor current" you get M916 as the first result

So I would say @deckingman s point about precise searches yielding precise answers still holds true.

As per "fuzzy matches" to searches, you already see that I get a number of matches that are not directly matching my search term. More than that and we get into the realm of the system sometimes helping too much, which is equally frustrating.

[nikscha]

@oliof
yeah that's not working so well...

And what if I spell "address" wrong? Not a single result, and the "did you mean..." are also wrong:

(what's exapansion?)

[nikscha]

@nikscha
Just now I wanted to update the firmware for a can expansion board, but searching for "gcode can board update" doesn't yield the right (or any) gcode. I need to open an article first (not the first one btw) and do a ctrl+f for update to find the right gcode...

But maybe I wasn't precise enough?
Lets try a more precise query, surely it will yield the precise result:

Nope, doesn't work.

If I remove the word "board" from the query, it does work....

This is the gcode I was looking for by the way:

Maybe I'm just so spoiled from google search reading my mind that this seems overly frustrating...

[droftarts]

@nikscha said in search for gcodes:

what's exapansion?

As it turns out, a typo on four wiki pages! Thanks for pointing this out, I've fixed them.

As for the search facility, at the moment it is all that is offered. Another option, as you have pointed out, is ctrl-f on the Gcode dictionary page. I'll talk to @T3P3Tony and see if it can be extended, or if wiki.js has any fuzzy search options.

Ian

[nikscha]

@droftarts
Welcome ^^

I hope I am not too negative, I really appreciate the work of the Duet team!

[Phaedrux]

I know it's a bit of a cop out, but google search may work better for you.

Screen Shot 2023-09-11 at 10.13.58 AM.png

[droftarts]

@nikscha typing “dictionary” first, then being a bit looser with your search terms can also help. Eg “dictionary firmware update” brings up M997 first.

Ian

[Herve_Smith]

@Phaedrux said in search for gcodes:

I know it's a bit of a cop out, but google search may work better for you.

This...

I do this a lot, as even searching for old topics on the forum 9 times out of 10 results in frustration, i worked out a long time ago as long as you have "duet" in the search term googles search results just wee's all over the forum and docs search facility .

[droftarts]

As shown in @Phaedrux 's screen shot, if you're using google, you can use a site-specific search, which will return results from solely the specified website. I use this a lot to search the forum.

For the forum, start your search with site:https://forum.duet3d.com/ with your search terms after.
For the wiki, start your search with site:https://docs.duet3d.com/ , again with your search terms after.

Ian