Don't artificially limit the rendering axes for CVRP environment

[ngastzepeda]

Description

Commented our the two lines of code that set the limits for the x and y axis, respectively.

Motivation and Context

Assuming all locs would be scaled to [0,1] let to rendering problems for instances that were not in fact scaled to [0,1].

Closes #258 .

Types of changes

What types of changes does your code introduce? Remove all that do not apply:

• Bug fix (non-breaking change which fixes an issue)

Checklist

Go over all the following points, and put an x in all the boxes that apply.
If you are unsure about any of these, don't hesitate to ask. We are here to help!

• My change requires a change to the documentation.
• I have updated the tests accordingly (required for a bug fix or a new feature).
• I have updated the documentation accordingly.

[ngastzepeda]

Set to draft for now, as we may choose to find a better solution than just not setting the axis limits.

[fedebotu]

Sounds good!
I am also thinking about a more systematic change:
How about we never impose any artificial limit in the render function, but instead return the ax?

For example:

def render(td, ..., return_ax=False):
   # Main function
   # ... 
   if return_ax:
      return ax

In this way, users can directly modify the plot style (including setting the x_lim and y_lim) afterwards:

ax = env.render(td, ..., return_ax=True):
ax.set_xlim(0, 1)
ax.set_ylim(0, 1)

WDYT?

cc @Estalisium, this should solve the plotting issue!

[ngastzepeda]

Sounds good! I am also thinking about a more systematic change: How about we never impose any artificial limit in the render function, but instead return the ax?

For example:

def render(td, ..., return_ax=False):
   # Main function
   # ... 
   if return_ax:
      return ax

In this way, users can directly modify the plot style (including setting the x_lim and y_lim) afterwards:

ax = env.render(td, ..., return_ax=True):
ax.set_xlim(0, 1)
ax.set_ylim(0, 1)

WDYT?

cc @Estalisium, this should solve the plotting issue!

I have not tested this, but feel free to push to this branch @fedebotu :)