Closed weiji14 closed 4 years ago
Current master works and says
gmt basemap -R2020-1-24T21:00/2020-1-25T00:00/0/1 -JX6c/2c -Bpa1Hg -Bsa45mfg45m -BNWse --MAP_GRID_CROSS_SIZE=3p -png lixo
basemap [WARNING]: Your primary y annotation interval exceeds the secondary interval.
basemap [WARNING]: GMT expects it to be the other way around (primary annotations are closest to axis, secondary are further away)
basemap [WARNING]: Consider correcting your command - proceeding with your selections
basemap [WARNING]: Your primary y tick interval exceeds the secondary interval.
basemap [WARNING]: GMT expects it to be the other way around (primary annotations are closest to axis, secondary are further away)
basemap [WARNING]: Consider correcting your command - proceeding with your selections
@joa-quim's one-liner works but @weiji14's modern mode script doesn't work.
I've tested the other parameters (FONT_ANNOT
, FORMAT_TIME_MAP
, MAP_ANNOT_OFFSET
, MAP_GRID_CROSS_SIZE
, MAP_TICK_LENGTH
, MAP_TICK_PEN
) which also set _PRIMARY
and _SECONDARY
settings at https://github.com/GenericMappingTools/pygmt/pull/411, and it seems to be only MAP_GRID_CROSS_SIZE
that doesn't work.
Edit: Can confirm that one-liner version works properly on 6.0.0 too.
gmt set MAP_GRID_CROSS_SIZE=3p
results in no change to gmt.conf. That is why using --gmt set MAP_GRID_CROSS_SIZE=3p works while the script fails. Will look at this.
Description of the problem
The
MAP_GRID_CROSS_SIZE
doesn't seem to be applied properly (to simultaneously changeMAP_GRID_CROSS_SIZE_PRIMARY
andMAP_GRID_CROSS_SIZE_SECONDARY
). Realized this when trying to write some unit tests to handle issue at https://github.com/GenericMappingTools/pygmt/issues/409.Full script that generated the error
Full error message
Actual outcome
Expected outcome
System information
gmt --version
): 6.0.0 (Build hb321953_2 from conda-forge)