Skip to content

Rename outfile parameter in surface to be outgrid #1441

Closed

Description

@weiji14

Description of the desired feature

As mentioned at #1439 (comment), most PyGMT functions which return a grid output have a parameter called outgrid, but the surface function uses outfile. It would be best to standardize the name to be outgrid instead.

G="outfile",

Should we deprecate the outfile parameter in 2 minor versions (at PyGMT v0.7.0) or 4 minor versions (at PyGMT v0.9.0)? Vote 👀 for 2 and 🎉 for 4.

Are you willing to help implement and maintain this feature? Someone can follow our deprecation policy steps at https://www.pygmt.org/v0.4.1/maintenance.html#backwards-compatibility-and-deprecation-policy to resolve this issue.

Activity

  1. added this to the 0.5.0 milestone on Aug 11, 2021
  2. added
    eswn-workshopGood issues for first-contributions during the ESWN-PyGMT workshop
    on Aug 17, 2021
  3. maxrjones commented on Aug 18, 2021

    @maxrjones
    Member

    This is somewhat related - I am not sure if it's worth a deprecation but I think we should decide on whether the parameter for tabular input is data or table for all modules moving forward. Currently, this is the distribution:

    data parameter: surface, wiggle, velo, rose, plot3d, plot, contour
    table parameter: blockmedian, blockmean, histogram
    other: grdtrack (points), text (textfiles)

    It would also be worthwhile to set a consistent order for the positional arguments x, y, [z], data, [outfile]

  4. maxrjones commented on Aug 19, 2021

    @maxrjones
    Member

    @obaney will be working on this issue!

  5. seisman commented on Sep 1, 2021

    @seisman
    Member

    This is somewhat related - I am not sure if it's worth a deprecation but I think we should decide on whether the parameter for tabular input is data or table for all modules moving forward. Currently, this is the distribution:

    data parameter: surface, wiggle, velo, rose, plot3d, plot, contour
    table parameter: blockmedian, blockmean, histogram
    other: grdtrack (points), text (textfiles)

    It would also be worthwhile to set a consistent order for the positional arguments x, y, [z], data, [outfile]

    Perhaps we need to open a separate issue to discuss it.

  6. weiji14 commented on Sep 1, 2021

    @weiji14
    MemberAuthor

    This is somewhat related - I am not sure if it's worth a deprecation but I think we should decide on whether the parameter for tabular input is data or table for all modules moving forward. Currently, this is the distribution:
    data parameter: surface, wiggle, velo, rose, plot3d, plot, contour
    table parameter: blockmedian, blockmean, histogram
    other: grdtrack (points), text (textfiles)
    It would also be worthwhile to set a consistent order for the positional arguments x, y, [z], data, [outfile]

    Perhaps we need to open a separate issue to discuss it.

    Yep, just opened #1479. Let's discuss there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    deprecationDeprecating a featureeswn-workshopGood issues for first-contributions during the ESWN-PyGMT workshopgood first issueGood for newcomershelp wantedHelping hands are appreciated

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions