set_spines features

[rcorfas]

possible to pass more data to the set_spines function, for example to adjust padding on individual axes?

[florisvb]

By padding, do you mean you want to move the spine+ticks closer/farther from the plot?

If so, I think you can do that with the adjust_spines function through the spine_location_offset. This will adjust all the spines on that axis. If you want independent control, that would have to be done via matplotlib functions (if it is possible), or we could extend the functionality of that function.

[psilentp]

Maybe we can add something through the spinespec tag that would be passed to adjust_spines function when set_spines are called. I was thinking attributes might be the most natural approach, but maybe there is a simpler way.

[rcorfas]

Sorry, I must be missing something obvious... But I can't seem to alter the spine/tick padding when I try to change the offset:

fifi.mpl_functions.adjust_spines(axis,['left', 'bottom'],spine_location_offset=20)

Here's the code from your function: spine_locations_dict = figurefirst_user_parameters.spine_locations for key in spine_locations.keys(): spine_locations_dict[key] = spine_locations[key] if spine_location_offset is not None: spine_locations_dict[key] = spine_location_offset

On Fri, Apr 27, 2018 at 9:53 AM, Theodore Lindsay notifications@github.com wrote:

Maybe we can add something through the spinespec tag that would be passed to adjust_spines function when set_spines are called. I was thinking attributes might be the most natural approach, but maybe there is a simpler way.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/FlyRanch/figurefirst/issues/33#issuecomment-385029991, or mute the thread https://github.com/notifications/unsubscribe-auth/Ak-N59a-oKD0uKkKL-vUVwwEhAvUofwjks5ts00mgaJpZM4Tna-2 .

[florisvb]

What happens? Error? Nothing? Are you making the adjust spines call before any savefig calls? What happens if you make the number truly enormous, like 1000?

Sent from my iPhone

On Jun 1, 2018, at 5:51 PM, rcorfas notifications@github.com wrote:

Sorry, I must be missing something obvious... But I can't seem to alter the spine/tick padding when I try to change the offset:

fifi.mpl_functions.adjust_spines(axis,['left', 'bottom'],spine_location_offset=20)

Here's the code from your function: spine_locations_dict = figurefirst_user_parameters.spine_locations for key in spine_locations.keys(): spine_locations_dict[key] = spine_locations[key] if spine_location_offset is not None: spine_locations_dict[key] = spine_location_offset

On Fri, Apr 27, 2018 at 9:53 AM, Theodore Lindsay notifications@github.com wrote:

Maybe we can add something through the spinespec tag that would be passed to adjust_spines function when set_spines are called. I was thinking attributes might be the most natural approach, but maybe there is a simpler way.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/FlyRanch/figurefirst/issues/33#issuecomment-385029991, or mute the thread https://github.com/notifications/unsubscribe-auth/Ak-N59a-oKD0uKkKL-vUVwwEhAvUofwjks5ts00mgaJpZM4Tna-2 .

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[rcorfas]

Yeah, nothing seems to happen. I did try "truly enormous numbers" haha. I also tried using some of the other adjust_spines parameters, and was able to alter xticks for example.

The adjust_spines call is made before savefig. However, I do make this call after my attempt to adjust_spines (below). Would it interfere? fifi.mpl_functions.set_spines(layout)

Thanks! Roman

On Fri, Jun 1, 2018 at 7:16 PM, Floris van Breugel <notifications@github.com

wrote:

What happens? Error? Nothing? Are you making the adjust spines call before any savefig calls? What happens if you make the number truly enormous, like 1000?

Sent from my iPhone

On Jun 1, 2018, at 5:51 PM, rcorfas notifications@github.com wrote:

Sorry, I must be missing something obvious... But I can't seem to alter the spine/tick padding when I try to change the offset:

fifi.mpl_functions.adjust_spines(axis,['left', 'bottom'],spine_location_offset=20)

Here's the code from your function: spine_locations_dict = figurefirst_user_parameters.spine_locations for key in spine_locations.keys(): spine_locations_dict[key] = spine_locations[key] if spine_location_offset is not None: spine_locations_dict[key] = spine_location_offset

On Fri, Apr 27, 2018 at 9:53 AM, Theodore Lindsay < notifications@github.com> wrote:

Maybe we can add something through the spinespec tag that would be passed to adjust_spines function when set_spines are called. I was thinking attributes might be the most natural approach, but maybe there is a simpler way.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/FlyRanch/figurefirst/issues/33# issuecomment-385029991, or mute the thread https://github.com/notifications/unsubscribe-auth/Ak-N59a-oKD0uKkKL- vUVwwEhAvUofwjks5ts00mgaJpZM4Tna-2 .

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub, or mute the thread.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/FlyRanch/figurefirst/issues/33#issuecomment-394049653, or mute the thread https://github.com/notifications/unsubscribe-auth/Ak-N5wcFEWdLU4RCTa3DVNSbJl9RwmHjks5t4fWWgaJpZM4Tna-2 .

[florisvb]

Yea that set_spines call could be your problem. What happens if you take it out? I don't think you'd need it if you're calling adjust_spines.

On Mon, Jun 4, 2018 at 12:15 PM rcorfas notifications@github.com wrote:

Yeah, nothing seems to happen. I did try "truly enormous numbers" haha. I also tried using some of the other adjust_spines parameters, and was able to alter xticks for example.

The adjust_spines call is made before savefig. However, I do make this call after my attempt to adjust_spines (below). Would it interfere? fifi.mpl_functions.set_spines(layout)

Thanks! Roman

On Fri, Jun 1, 2018 at 7:16 PM, Floris van Breugel < notifications@github.com

wrote:

What happens? Error? Nothing? Are you making the adjust spines call before any savefig calls? What happens if you make the number truly enormous, like 1000?

Sent from my iPhone

On Jun 1, 2018, at 5:51 PM, rcorfas notifications@github.com wrote:

Sorry, I must be missing something obvious... But I can't seem to alter the spine/tick padding when I try to change the offset:

fifi.mpl_functions.adjust_spines(axis,['left', 'bottom'],spine_location_offset=20)

Here's the code from your function: spine_locations_dict = figurefirst_user_parameters.spine_locations for key in spine_locations.keys(): spine_locations_dict[key] = spine_locations[key] if spine_location_offset is not None: spine_locations_dict[key] = spine_location_offset

On Fri, Apr 27, 2018 at 9:53 AM, Theodore Lindsay < notifications@github.com> wrote:

Maybe we can add something through the spinespec tag that would be passed to adjust_spines function when set_spines are called. I was thinking attributes might be the most natural approach, but maybe there is a simpler way.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/FlyRanch/figurefirst/issues/33# issuecomment-385029991, or mute the thread < https://github.com/notifications/unsubscribe-auth/Ak-N59a-oKD0uKkKL- vUVwwEhAvUofwjks5ts00mgaJpZM4Tna-2> .

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub, or mute the thread.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/FlyRanch/figurefirst/issues/33#issuecomment-394049653>, or mute the thread < https://github.com/notifications/unsubscribe-auth/Ak-N5wcFEWdLU4RCTa3DVNSbJl9RwmHjks5t4fWWgaJpZM4Tna-2

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/FlyRanch/figurefirst/issues/33#issuecomment-394448939, or mute the thread https://github.com/notifications/unsubscribe-auth/AAPCPAnag_rXyEcOSWQJ1_tSg-TuwkXOks5t5XlHgaJpZM4Tna-2 .

-- Floris van Breugel Moore-Sloan / Sackler Fellow at UW, Seattle eScience Institute / Departments of Biology & Applied Math Science: http://www.florisvanbreugel.com

2018 Calendars: www.artinnaturephotography.com/product/2018-calendar/

Wildlife and Landscape Photographer Galleries: http://www.ArtInNaturePhotography.com/ Blog: http://www.ArtInNaturePhotography.com/wordpress/

[rcorfas]

Thanks Floris, I removed the set_spines call, but that didn't help me control the adjust_spines offset. Another problem is that by removing set_spines call I lose all of the spines tag assignments I made in my layout file, right? Is there a way to selectively adjust spines offset on only certain axes in my layout, while still enacting the spines tags from the layout file? I hope this makes sense -- not sure about all my vocab here and I'm probably missing some basic facts. Apologies. Thanks, Roman

On Mon, Jun 4, 2018 at 11:35 AM, Floris van Breugel < notifications@github.com> wrote:

Yea that set_spines call could be your problem. What happens if you take it out? I don't think you'd need it if you're calling adjust_spines.

On Mon, Jun 4, 2018 at 12:15 PM rcorfas notifications@github.com wrote:

Yeah, nothing seems to happen. I did try "truly enormous numbers" haha. I also tried using some of the other adjust_spines parameters, and was able to alter xticks for example.

The adjust_spines call is made before savefig. However, I do make this call after my attempt to adjust_spines (below). Would it interfere? fifi.mpl_functions.set_spines(layout)

Thanks! Roman

On Fri, Jun 1, 2018 at 7:16 PM, Floris van Breugel < notifications@github.com

wrote:

What happens? Error? Nothing? Are you making the adjust spines call before any savefig calls? What happens if you make the number truly enormous, like 1000?

Sent from my iPhone

On Jun 1, 2018, at 5:51 PM, rcorfas notifications@github.com wrote:

Sorry, I must be missing something obvious... But I can't seem to alter the spine/tick padding when I try to change the offset:

fifi.mpl_functions.adjust_spines(axis,['left', 'bottom'],spine_location_offset=20)

Here's the code from your function: spine_locations_dict = figurefirst_user_parameters.spine_locations for key in spine_locations.keys(): spine_locations_dict[key] = spine_locations[key] if spine_location_offset is not None: spine_locations_dict[key] = spine_location_offset

On Fri, Apr 27, 2018 at 9:53 AM, Theodore Lindsay < notifications@github.com> wrote:

Maybe we can add something through the spinespec tag that would be passed to adjust_spines function when set_spines are called. I was thinking attributes might be the most natural approach, but maybe there is a simpler way.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/FlyRanch/figurefirst/issues/33# issuecomment-385029991, or mute the thread < https://github.com/notifications/unsubscribe-auth/Ak-N59a-oKD0uKkKL- vUVwwEhAvUofwjks5ts00mgaJpZM4Tna-2> .

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub, or mute the thread.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/FlyRanch/figurefirst/issues/33#issuecomment-394049653 , or mute the thread < https://github.com/notifications/unsubscribe-auth/Ak- N5wcFEWdLU4RCTa3DVNSbJl9RwmHjks5t4fWWgaJpZM4Tna-2

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/FlyRanch/figurefirst/issues/33# issuecomment-394448939, or mute the thread https://github.com/notifications/unsubscribe- auth/AAPCPAnag_rXyEcOSWQJ1_tSg-TuwkXOks5t5XlHgaJpZM4Tna-2 .

-- Floris van Breugel Moore-Sloan / Sackler Fellow at UW, Seattle eScience Institute / Departments of Biology & Applied Math Science: http://www.florisvanbreugel.com

2018 Calendars: www.artinnaturephotography.com/product/2018-calendar/

Wildlife and Landscape Photographer Galleries: http://www.ArtInNaturePhotography.com/ Blog: http://www.ArtInNaturePhotography.com/wordpress/

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/FlyRanch/figurefirst/issues/33#issuecomment-394454973, or mute the thread https://github.com/notifications/unsubscribe-auth/Ak-N5yN3rIXsqXyA-eeGrBTEJ3lEblqGks5t5X4DgaJpZM4Tna-2 .

[psilentp]

I've got a branch 'pass_more_to_spinespec' that lets you pass the padding features to the adjust_spines function via the layout document, but I haven't got it to the point where I can merge it with the master yet (it only works with the spine_locations_offset field). Mostly I'm a little unsure what the additional kwargs of the adjust_spines function mean. Any chance we could add a little more to the adjust_spines docstring?

[florisvb]

Docstring updated and pushed.. let me know if anything doesn't make sense. It is a little hacky being built on some legacy code (smart_bounds stuff), and not messing up loglog plots (default_ticks kwarg). But it seems to work for all the use cases I've been throwing at it.

• Floris

On Mon, Jun 4, 2018 at 3:49 PM Theodore Lindsay notifications@github.com wrote:

I've got a branch 'pass_more_to_spinespec' that lets you pass the padding features to the adjust_spines function via the layout document, but I haven't got it to the point where I can merge it with the master yet (it only works with the spine_locations_offset field). Mostly I'm a little unsure what the additional kwargs of the adjust_spines function mean. Any chance we could add a little more to the adjust_spines docstring?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/FlyRanch/figurefirst/issues/33#issuecomment-394511308, or mute the thread https://github.com/notifications/unsubscribe-auth/AAPCPO6tbI4gqKjlQLxEvPrUBDqQudtZks5t5at0gaJpZM4Tna-2 .

-- Floris van Breugel Moore-Sloan / Sackler Fellow at UW, Seattle eScience Institute / Departments of Biology & Applied Math Science: http://www.florisvanbreugel.com

2018 Calendars: www.artinnaturephotography.com/product/2018-calendar/

Wildlife and Landscape Photographer Galleries: http://www.ArtInNaturePhotography.com/ Blog: http://www.ArtInNaturePhotography.com/wordpress/

[rcorfas]

Thanks Floris and Thad! Not sure what most of that means tbh, but I will check it out soon and see if I can figure it out. Roman

On Tue, Jun 5, 2018 at 10:55 AM, Floris van Breugel < notifications@github.com> wrote:

Docstring updated and pushed.. let me know if anything doesn't make sense. It is a little hacky being built on some legacy code (smart_bounds stuff), and not messing up loglog plots (default_ticks kwarg). But it seems to work for all the use cases I've been throwing at it.

• Floris

On Mon, Jun 4, 2018 at 3:49 PM Theodore Lindsay notifications@github.com wrote:

I've got a branch 'pass_more_to_spinespec' that lets you pass the padding features to the adjust_spines function via the layout document, but I haven't got it to the point where I can merge it with the master yet (it only works with the spine_locations_offset field). Mostly I'm a little unsure what the additional kwargs of the adjust_spines function mean. Any chance we could add a little more to the adjust_spines docstring?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/FlyRanch/figurefirst/issues/33# issuecomment-394511308, or mute the thread https://github.com/notifications/unsubscribe-auth/ AAPCPO6tbI4gqKjlQLxEvPrUBDqQudtZks5t5at0gaJpZM4Tna-2 .

-- Floris van Breugel Moore-Sloan / Sackler Fellow at UW, Seattle eScience Institute / Departments of Biology & Applied Math Science: http://www.florisvanbreugel.com

2018 Calendars: www.artinnaturephotography.com/product/2018-calendar/

Wildlife and Landscape Photographer Galleries: http://www.ArtInNaturePhotography.com/ Blog: http://www.ArtInNaturePhotography.com/wordpress/

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/FlyRanch/figurefirst/issues/33#issuecomment-394802605, or mute the thread https://github.com/notifications/unsubscribe-auth/Ak-N5-cImUGlbJBU7nVXvFyVtUL7nab7ks5t5sYmgaJpZM4Tna-2 .

[rcorfas]

Sorry, amateur hour here... I'm not sure if the new feature has been implemented, but if so, how can I use it? I repulled fifi. Is that right? Now what? Thanks! Roman

On Tue, Jun 5, 2018 at 10:55 AM, Floris van Breugel < notifications@github.com> wrote:

Docstring updated and pushed.. let me know if anything doesn't make sense. It is a little hacky being built on some legacy code (smart_bounds stuff), and not messing up loglog plots (default_ticks kwarg). But it seems to work for all the use cases I've been throwing at it.

• Floris

On Mon, Jun 4, 2018 at 3:49 PM Theodore Lindsay notifications@github.com wrote:

I've got a branch 'pass_more_to_spinespec' that lets you pass the padding features to the adjust_spines function via the layout document, but I haven't got it to the point where I can merge it with the master yet (it only works with the spine_locations_offset field). Mostly I'm a little unsure what the additional kwargs of the adjust_spines function mean. Any chance we could add a little more to the adjust_spines docstring?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/FlyRanch/figurefirst/issues/33# issuecomment-394511308, or mute the thread https://github.com/notifications/unsubscribe-auth/ AAPCPO6tbI4gqKjlQLxEvPrUBDqQudtZks5t5at0gaJpZM4Tna-2 .

-- Floris van Breugel Moore-Sloan / Sackler Fellow at UW, Seattle eScience Institute / Departments of Biology & Applied Math Science: http://www.florisvanbreugel.com

2018 Calendars: www.artinnaturephotography.com/product/2018-calendar/

Wildlife and Landscape Photographer Galleries: http://www.ArtInNaturePhotography.com/ Blog: http://www.ArtInNaturePhotography.com/wordpress/

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/FlyRanch/figurefirst/issues/33#issuecomment-394802605, or mute the thread https://github.com/notifications/unsubscribe-auth/Ak-N5-cImUGlbJBU7nVXvFyVtUL7nab7ks5t5sYmgaJpZM4Tna-2 .

[rcorfas]

I'm pretty lost on how to proceed -- apologies! Does my general question make sense, or is there any other info I can provide to clarify? Thanks, Roman

On Thu, Jun 21, 2018 at 2:11 PM, Roman Corfas roman.corfas@gmail.com wrote:

Sorry, amateur hour here... I'm not sure if the new feature has been implemented, but if so, how can I use it? I repulled fifi. Is that right? Now what? Thanks! Roman

On Tue, Jun 5, 2018 at 10:55 AM, Floris van Breugel < notifications@github.com> wrote:

Docstring updated and pushed.. let me know if anything doesn't make sense. It is a little hacky being built on some legacy code (smart_bounds stuff), and not messing up loglog plots (default_ticks kwarg). But it seems to work for all the use cases I've been throwing at it.

• Floris

On Mon, Jun 4, 2018 at 3:49 PM Theodore Lindsay <notifications@github.com

wrote:

I've got a branch 'pass_more_to_spinespec' that lets you pass the padding features to the adjust_spines function via the layout document, but I haven't got it to the point where I can merge it with the master yet (it only works with the spine_locations_offset field). Mostly I'm a little unsure what the additional kwargs of the adjust_spines function mean. Any chance we could add a little more to the adjust_spines docstring?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/FlyRanch/figurefirst/issues/33#issuecomm ent-394511308, or mute the thread https://github.com/notifications/unsubscribe-auth/AAPCPO6tb I4gqKjlQLxEvPrUBDqQudtZks5t5at0gaJpZM4Tna-2 .

-- Floris van Breugel Moore-Sloan / Sackler Fellow at UW, Seattle eScience Institute / Departments of Biology & Applied Math Science: http://www.florisvanbreugel.com

2018 Calendars: www.artinnaturephotography.com/product/2018-calendar/

Wildlife and Landscape Photographer Galleries: http://www.ArtInNaturePhotography.com/ Blog: http://www.ArtInNaturePhotography.com/wordpress/

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/FlyRanch/figurefirst/issues/33#issuecomment-394802605, or mute the thread https://github.com/notifications/unsubscribe-auth/Ak-N5-cImUGlbJBU7nVXvFyVtUL7nab7ks5t5sYmgaJpZM4Tna-2 .

[psilentp]

The development branch doesn't pass the tests so I haven't merged it with the master yet... I think it need a little more work.

[rcorfas]

Ah ok! Thanks!

On Jun 28, 2018, at 16:02, Theodore Lindsay notifications@github.com wrote:

The development branch doesn't pass the tests so I haven't merged it with the master yet... I think it need a little more work.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[rcorfas]

Hey guys, sorry to keep pestering you! But just need to know if I should work around this, or if you think this might get implemented at some point? Thanks, Roman

On Thu, Jun 28, 2018 at 7:03 PM, Roman Corfas roman.corfas@gmail.com wrote:

Ah ok! Thanks!

On Jun 28, 2018, at 16:02, Theodore Lindsay notifications@github.com wrote:

The development branch doesn't pass the tests so I haven't merged it with the master yet... I think it need a little more work.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/FlyRanch/figurefirst/issues/33#issuecomment-401198537, or mute the thread https://github.com/notifications/unsubscribe-auth/Ak-N53pSJ0PtqVMTqwR78aIXiEJ70qRGks5uBWCagaJpZM4Tna-2 .

[florisvb]

I think thad probably has his hands full for a little while with the insight thing..

I would say for now try and work around it if you can. You should be able to do everything spine-wise that you need outside of the figurefirst environment. Just make all your own axis changes after any figurefirst adjust_spines type calls, and before you write the figure to the svg.

On Fri, Jul 13, 2018 at 10:38 AM rcorfas notifications@github.com wrote:

Hey guys, sorry to keep pestering you! But just need to know if I should work around this, or if you think this might get implemented at some point? Thanks, Roman

On Thu, Jun 28, 2018 at 7:03 PM, Roman Corfas roman.corfas@gmail.com wrote:

Ah ok! Thanks!

On Jun 28, 2018, at 16:02, Theodore Lindsay notifications@github.com wrote:

The development branch doesn't pass the tests so I haven't merged it with the master yet... I think it need a little more work.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/FlyRanch/figurefirst/issues/33#issuecomment-401198537>, or mute the thread < https://github.com/notifications/unsubscribe-auth/Ak-N53pSJ0PtqVMTqwR78aIXiEJ70qRGks5uBWCagaJpZM4Tna-2

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/FlyRanch/figurefirst/issues/33#issuecomment-404902805, or mute the thread https://github.com/notifications/unsubscribe-auth/AAPCPKCft5jwUDJaTo5V-tLVRJzibsc2ks5uGNskgaJpZM4Tna-2 .

-- Floris van Breugel Moore-Sloan / Sackler Fellow at UW, Seattle eScience Institute / Departments of Biology & Applied Math Science: http://www.florisvanbreugel.com

2018 Calendars: www.artinnaturephotography.com/product/2018-calendar/

Wildlife and Landscape Photographer Galleries: http://www.ArtInNaturePhotography.com/ Blog: http://www.ArtInNaturePhotography.com/wordpress/

[rcorfas]

Thanks Floris! And good luck Thad!

On Fri, Jul 13, 2018 at 11:04 AM, Floris van Breugel < notifications@github.com> wrote:

I think thad probably has his hands full for a little while with the insight thing..

I would say for now try and work around it if you can. You should be able to do everything spine-wise that you need outside of the figurefirst environment. Just make all your own axis changes after any figurefirst adjust_spines type calls, and before you write the figure to the svg.

On Fri, Jul 13, 2018 at 10:38 AM rcorfas notifications@github.com wrote:

Hey guys, sorry to keep pestering you! But just need to know if I should work around this, or if you think this might get implemented at some point? Thanks, Roman

On Thu, Jun 28, 2018 at 7:03 PM, Roman Corfas roman.corfas@gmail.com wrote:

Ah ok! Thanks!

On Jun 28, 2018, at 16:02, Theodore Lindsay notifications@github.com wrote:

The development branch doesn't pass the tests so I haven't merged it with the master yet... I think it need a little more work.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/FlyRanch/figurefirst/issues/33#issuecomment-401198537 , or mute the thread < https://github.com/notifications/unsubscribe-auth/Ak- N53pSJ0PtqVMTqwR78aIXiEJ70qRGks5uBWCagaJpZM4Tna-2

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/FlyRanch/figurefirst/issues/33# issuecomment-404902805, or mute the thread https://github.com/notifications/unsubscribe-auth/AAPCPKCft5jwUDJaTo5V- tLVRJzibsc2ks5uGNskgaJpZM4Tna-2 .

-- Floris van Breugel Moore-Sloan / Sackler Fellow at UW, Seattle eScience Institute / Departments of Biology & Applied Math Science: http://www.florisvanbreugel.com

2018 Calendars: www.artinnaturephotography.com/product/2018-calendar/

Wildlife and Landscape Photographer Galleries: http://www.ArtInNaturePhotography.com/ Blog: http://www.ArtInNaturePhotography.com/wordpress/

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/FlyRanch/figurefirst/issues/33#issuecomment-404909592, or mute the thread https://github.com/notifications/unsubscribe-auth/Ak-N505_wI0I3IZDj5SXfWQa98C1JA_yks5uGOEmgaJpZM4Tna-2 .

[florisvb]

Just checking in here - this is the call I usually use, does this not do what you want?

mpl_functions.adjust_spines(ax, ['left', 'bottom'], spine_locations={'left': 2.5, 'bottom': 2.5}, linewidth=0.5, tick_length=2.5)

(note: I added the tick_length option recently)

[rcorfas]

Yeah I've sorted out a solution using this. Thanks!

On Sat, Aug 25, 2018 at 10:42 AM, Floris van Breugel < notifications@github.com> wrote:

Just checking in here - this is the call I usually use, does this not do what you want?

mpl_functions.adjust_spines(ax, ['left', 'bottom'], spine_locations={'left': 2.5, 'bottom': 2.5}, linewidth=0.5, tick_length=2.5)

(note: I added the tick_length option recently)

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/FlyRanch/figurefirst/issues/33#issuecomment-415985331, or mute the thread https://github.com/notifications/unsubscribe-auth/Ak-N56wowosQ2GFbgGwfqzTz6iBA3sMrks5uUYx5gaJpZM4Tna-2 .

[florisvb]

Great, I'll go ahead and close this then.