Re: [GRASS-dev] Adding an expert mode to the parser

On Wed, Sep 28, 2016 at 4:35 PM, Markus Metz wrote: > On Tue, Sep 27, 2016 at 5:55 PM, Vaclav Petras > wrote: > > > > On Mon, Sep 26, 2016 at 5:50 PM, Vaclav Petras > wrote: > >> > >> If the --help is just for scanning

Re: [GRASS-dev] Adding an expert mode to the parser

Hi, [snip] > > > > As an example, when aiming at processing all Sentinel-2 tiles > > globally, we speak about currently 73000 scenes * up-to-16 tiles along > > with global data, analysis on top of other global data is more complex > > when doing each job in its own mapset and reintegrate it in a

Re: [GRASS-dev] Adding an expert mode to the parser

On Sun, Sep 25, 2016 at 9:49 PM, Markus Neteler wrote: > On Fri, Sep 23, 2016 at 11:30 PM, Markus Metz > wrote: >> On Fri, Sep 23, 2016 at 11:22 PM, Markus Neteler wrote: >>> On Fri, Sep 23, 2016 at 11:05 PM, Markus Metz >>>

Re: [GRASS-dev] Adding an expert mode to the parser

On Tue, Sep 27, 2016 at 5:55 PM, Vaclav Petras wrote: > > On Mon, Sep 26, 2016 at 5:50 PM, Vaclav Petras wrote: >> >> If the --help is just for scanning and the issue is that it simply too >> long, hiding some parameters is not the only option we have.

Re: [GRASS-dev] Adding an expert mode to the parser

On Tue, Sep 27, 2016 at 5:38 PM, Sören Gebbert wrote: > However, the correct use of GRASS_REGION is still unclear to me. There is a function in grass.script [1] which can generate the right string. It calls g.region with -u, so you can modify the region with

Re: [GRASS-dev] Adding an expert mode to the parser

On Tue, Sep 27, 2016 at 5:01 PM, Sören Gebbert wrote: > From my understanding, the GRASS_REGION environmental variable is > supported by G_get_window() [1]. However, most raster modules > uses Rast_window_rows() and Rast_window_cols() to get the current >

Re: [GRASS-dev] Adding an expert mode to the parser

Hi, > On Sun, Sep 25, 2016 at 5:40 PM, Sören Gebbert < >> soerengebb...@googlemail.com> wrote: >> >>> >r.mapclac --raster-region= --north= --south= --west= --east= --res= >--ewres= --nsres= --vect-region --raster-align= ... >>> >> I like this in the sense that if the region setting for

Re: [GRASS-dev] Adding an expert mode to the parser

Hi, 2016-09-26 4:16 GMT+02:00 Vaclav Petras : > > On Sun, Sep 25, 2016 at 5:40 PM, Sören Gebbert < > soerengebb...@googlemail.com> wrote: > >> >r.mapclac --raster-region= --north= --south= --west= --east= --res= >>> >--ewres= --nsres= --vect-region --raster-align= ... >>>

Re: [GRASS-dev] Adding an expert mode to the parser

On Mon, Sep 26, 2016 at 5:50 PM, Vaclav Petras wrote: > If the --help is just for scanning and the issue is that it simply too > long, hiding some parameters is not the only option we have. For many (and > more in the future hopefully) parameters we have (short) label and

Re: [GRASS-dev] Adding an expert mode to the parser

On Tue, Sep 27, 2016 at 9:15 AM, Margherita Di Leo wrote: > Hi, > > On Tue, Sep 27, 2016 at 7:13 AM, Moritz Lennert < > mlenn...@club.worldonline.be> wrote: > >> On 26/09/16 23:50, Vaclav Petras wrote: >> >>> >>> On Mon, Sep 26, 2016 at 5:24 PM, Veronica Andreo

Re: [GRASS-dev] Adding an expert mode to the parser

+1 On Mon, Sep 26, 2016 at 6:11 PM, Vaclav Petras wrote: > > On Fri, Sep 23, 2016 at 5:22 PM, Markus Neteler wrote: > >> * various commands: "Use the low-memory version" - also more advanced > > > I guess this is a typical example where we need to be

Re: [GRASS-dev] Adding an expert mode to the parser

Moritz Lennert writes: > On 26/09/16 23:50, Vaclav Petras wrote: >> >> On Mon, Sep 26, 2016 at 5:24 PM, Veronica Andreo > > wrote: >> >> I'm with MaDi in that if I see a very long list of flags and >>

Re: [GRASS-dev] Adding an expert mode to the parser

Hi, On Tue, Sep 27, 2016 at 7:13 AM, Moritz Lennert < mlenn...@club.worldonline.be> wrote: > On 26/09/16 23:50, Vaclav Petras wrote: > >> >> On Mon, Sep 26, 2016 at 5:24 PM, Veronica Andreo > > wrote: >> >> I'm with MaDi in that if I see a

Re: [GRASS-dev] Adding an expert mode to the parser

On 26/09/16 23:50, Vaclav Petras wrote: On Mon, Sep 26, 2016 at 5:24 PM, Veronica Andreo > wrote: I'm with MaDi in that if I see a very long list of flags and parameters in the terminal when using --h, i just go to the manual... I

Re: [GRASS-dev] Adding an expert mode to the parser

On Fri, Sep 23, 2016 at 5:22 PM, Markus Neteler wrote: > * various commands: "Use the low-memory version" - also more advanced I guess this is a typical example where we need to be careful. I can imagine a situation when a beginner has a lot of data and low-end hardware. By

Re: [GRASS-dev] Adding an expert mode to the parser

On Fri, Sep 23, 2016 at 5:22 PM, Markus Neteler wrote: > Maybe not hide then but at least group the parameters and flags rather > than alpha-order or random mix. > This is something which can be done right now. The options and flags are presented in the order as they are

Re: [GRASS-dev] Adding an expert mode to the parser

On Mon, Sep 26, 2016 at 5:24 PM, Veronica Andreo wrote: > I'm with MaDi in that if I see a very long list of flags and parameters in > the terminal when using --h, i just go to the manual... I just use --h in > CLI for a quick recalling of flags/options... A reduced list of

Re: [GRASS-dev] Adding an expert mode to the parser

Hello I'm with MaDi in that if I see a very long list of flags and parameters in the terminal when using --h, i just go to the manual... I just use --h in CLI for a quick recalling of flags/options... A reduced list of most commonly used flags would be nice, but still keep the possibility to get

Re: [GRASS-dev] Adding an expert mode to the parser

Hi, On Fri, Sep 23, 2016 at 12:00 AM, Markus Neteler wrote: > Hi, > > in order to not hinder the addition of important new flags/parameters > to modules while keeping things optionally easy it would be good to > implement some expert mode to the parser. > > The flags and

Re: [GRASS-dev] Adding an expert mode to the parser

:28 To: Markus Neteler <nete...@osgeo.org> Cc: GRASS developers list <grass-dev@lists.osgeo.org>; Markus Metz <markus.metz.gisw...@gmail.com> Subject: Re: [GRASS-dev] Adding an expert mode to the parser On Sun, Sep 25, 2016 at 3:49 PM, Markus Neteler <nete...@osgeo.org<

Re: [GRASS-dev] Adding an expert mode to the parser

On Sun, Sep 25, 2016 at 3:49 PM, Markus Neteler wrote: > when doing each job in its own mapset and reintegrate it in a single > target mapset as if able to process then in parallel in one mapset by > simply specifying the respective region to the command of interest. > Yes,

Re: [GRASS-dev] Adding an expert mode to the parser

On Sun, Sep 25, 2016 at 5:40 PM, Sören Gebbert wrote: > >r.mapclac --raster-region= --north= --south= --west= --east= --res= >> >--ewres= --nsres= --vect-region --raster-align= ... >> > I like this in the sense that if the region setting for the module is something

Re: [GRASS-dev] Adding an expert mode to the parser

[snip] > >r.mapclac --raster-region= --north= --south= --west= --east= --res= > >--ewres= --nsres= --vect-region --raster-align= ... > > Can't you do this at a higher level, i.e using the GRASS Python API's > use_temp_region ? > This is exactly what i'm doing right now[1,2], covering a single

Re: [GRASS-dev] Adding an expert mode to the parser

Hi, Here an example of hidden region settings for modules utilized in the temporal framework: Imagine you have a Landsat location that contains many thousand scenes (time series) from all over the world including all bands. Each band of the time series is managed in a specific space-time dataset.

Re: [GRASS-dev] Adding an expert mode to the parser

On Fri, Sep 23, 2016 at 11:30 PM, Markus Metz wrote: > On Fri, Sep 23, 2016 at 11:22 PM, Markus Neteler wrote: >> On Fri, Sep 23, 2016 at 11:05 PM, Markus Metz >> wrote: >>> On Fri, Sep 23, 2016 at 1:11 PM, Markus

Re: [GRASS-dev] Adding an expert mode to the parser

On Fri, Sep 23, 2016 at 11:22 PM, Markus Neteler wrote: > On Fri, Sep 23, 2016 at 11:05 PM, Markus Metz > wrote: >> On Fri, Sep 23, 2016 at 1:11 PM, Markus Neteler wrote: > ... >> Your motivation is to provide a specialized

Re: [GRASS-dev] Adding an expert mode to the parser

On Fri, Sep 23, 2016 at 11:05 PM, Markus Metz wrote: > On Fri, Sep 23, 2016 at 1:11 PM, Markus Neteler wrote: ... > Your motivation is to provide a specialized CLI interface for HPC > processing? No, not the case. > We used GRASS with HPC

Re: [GRASS-dev] Adding an expert mode to the parser

On Fri, Sep 23, 2016 at 1:11 PM, Markus Neteler wrote: > On Fri, Sep 23, 2016 at 10:15 AM, Moritz Lennert > wrote: >> On 23/09/16 02:37, Anna Petrášová wrote: > ... >>> How do we decide which options are advanced. > > We simply keep 95% of all

Re: [GRASS-dev] Adding an expert mode to the parser

On 23/09/16 13:11, Markus Neteler wrote: On Fri, Sep 23, 2016 at 10:15 AM, Moritz Lennert > wrote: On 23/09/16 02:37, Anna Petrášová wrote: ... Probably not so complicated, but I would be more concerned with the decisions

Re: [GRASS-dev] Adding an expert mode to the parser

On Fri, Sep 23, 2016 at 10:15 AM, Moritz Lennert < mlenn...@club.worldonline.be> wrote: > On 23/09/16 02:37, Anna Petrášová wrote: ... >> Probably not so complicated, but I would be more concerned with the >> decisions coming with this. For example, what should the online manual >> show? Using

Re: [GRASS-dev] Adding an expert mode to the parser

On 23/09/16 02:37, Anna Petrášová wrote: On Thu, Sep 22, 2016 at 6:00 PM, Markus Neteler wrote: Hi, in order to not hinder the addition of important new flags/parameters to modules while keeping things optionally easy it would be good to implement some expert mode to the

Re: [GRASS-dev] Adding an expert mode to the parser

On Thu, Sep 22, 2016 at 6:00 PM, Markus Neteler wrote: > Hi, > > in order to not hinder the addition of important new flags/parameters > to modules while keeping things optionally easy it would be good to > implement some expert mode to the parser. > > The flags and parameters

[GRASS-dev] Adding an expert mode to the parser

Hi, in order to not hinder the addition of important new flags/parameters to modules while keeping things optionally easy it would be good to implement some expert mode to the parser. The flags and parameters for advanced users should be hidden by default (maybe by using an extra definition in