First impressions
183 views
Skip to first unread message
Julio Pascual Miqueleiz
Jun 29, 2022, 10:57:05 AM6/29/22
to pypsa
Hello:
My name is Julio, I'm a professor at UPNA (Spain) and I am just new to PyPSA/PyPSA-Eur. Having wanted to try it for quite a long time I have finally found the time to do it.
With this first message I wanted to, firstly, thank Tom Brown, Fabian Neumann and all other developers for this amazing software, the clear documentation and the tutorials.
Also, I would like to share my first impressions, typos (or not) that I've found in the documentation and workarounds that I had to use when running the basic tutorials. This would be my small contribution after my first days of use and I hope it is useful for someone. I must say that not only I'm new to PyPSA but also to Python so, sorry in advance if something is really obvious or doesn't make sense. Here I go:
PyPSA documentation
Quick-start (https://pypsa.readthedocs.io/en/latest/quick_start.html):
I think that last paragraph of Quick Start should say ‘reactive power’ instead of ‘inactive power’.
Meshed AC_DC (https://pypsa.readthedocs.io/en/latest/examples/ac-dc-lopf.html):
Example did not work as it is. Error at ‘network.lopf();’. Worked with ‘network.lopf(pyomo=False);’.
PyPSA-Eur documentationTutorial (https://pypsa-eur.readthedocs.io/en/latest/tutorial.html#):
Tried the tutorial but failed on first try as ipotp could not be found when running the sanakemake. After several attempts for fixing this issue, what finally worked was to downgrade ipopt to 3.11.1.
Subsection ‘How to customise PyPSA-Eur?’: seems like the last two code boxes are not related to the explanatory text right before them (those talking about the selection of ERA-5 or SARAH-2 and the selection of the optimizer).
Subsection ‘How to analyse solved networks?’: the link to PyPSA examples does not work.
Wildcards (https://pypsa-eur.readthedocs.io/en/latest/wildcards.html):
It would be useful to have a template of the snakemake code line as first thing in this page. Something like what appears in the Tutorial subsection ‘How to use the snakemake rules?’ (elec_s{simpl}_{clusters}_ec_l{ll}_{opts}.nc). Even though, not all wildcards are shown in that example; wildcards after {opts} seem to be missing, i.e., {country}, {cutout}, {technology}, {attr} and {ext}, although maybe they are not intended to be used the way I think...
Configuration (https://pypsa-eur.readthedocs.io/en/latest/configuration.html):
snapshots > [closed] > Description: It says ‘Make the time interval closed to the [left], [right], or both sides [None]’. I may be wrong but it seems like [None] means *open* on both sides.
Preparing Networks(https://pypsa-eur.readthedocs.io/en/latest/preparation.html):
Retrieve_databundle. I think where it says 19 MB should say 197 MB?
Finally, a more
general comment. I tried to analyse the resulting networks using Spyder in the
pypsa-eur environment but Spyder could not be opened. Seems like a problem with
jinja2. I realised that in the base environment, where Spyder works for me, the version
of jinja2 is 2.11.3 but in the pypsa-eur environment is 3.1.2. I unsuccessfully
tried to downgrade jinja2. So I couldn’t solve it but, in any case, I can analyse
the network under other environments or using other Python IDEs.
As I said, I am just starting (only 3 days since I installed it) so I guess I will be around here for the next days/weeks/months.
Once again, thank you all, and see you around,
Julio
Julio Pascual Miqueleiz
Jun 29, 2022, 10:59:22 AM6/29/22
to pypsa
P.S.: I'm working on Windows 10, Python 3.9.12 and everything managed with Anaconda.
Tom Brown
Jun 29, 2022, 12:03:12 PM6/29/22
to py...@googlegroups.com
Thanks Julio for the feedback!
We'll try and fix those bugs in the documentation over the next few days
- some of it has organically grown and needs correcting.
Best wishes,
Tom
On 29/06/2022 16:57, Julio Pascual Miqueleiz wrote:
> Externe E-Mail: Oeffnen Sie Anhaenge oder Links nur, wenn Sie der Quelle vertrauen.
> External E-Mail: Be cautious before clicking any link or attachment!
> <https://pypsa.readthedocs.io/en/latest/quick_start.html>):
> (https://pypsa.readthedocs.io/en/latest/examples/ac-dc-lopf.html
> <https://pypsa.readthedocs.io/en/latest/examples/ac-dc-lopf.html>):
> <https://pypsa-eur.readthedocs.io/en/latest/tutorial.html#>):
> examples does not work.
>
> *Wildcards *(https://pypsa-eur.readthedocs.io/en/latest/wildcards.html
> <https://pypsa-eur.readthedocs.io/en/latest/wildcards.html>):
> (https://pypsa-eur.readthedocs.io/en/latest/configuration.html
> <https://pypsa-eur.readthedocs.io/en/latest/configuration.html>):
> Networks*(https://pypsa-eur.readthedocs.io/en/latest/preparation.html
> <https://pypsa-eur.readthedocs.io/en/latest/preparation.html>):
> You received this message because you are subscribed to the Google
> Groups "pypsa" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to pypsa+un...@googlegroups.com
> <mailto:pypsa+un...@googlegroups.com>.
> To view this discussion on the web, visit
> https://groups.google.com/d/msgid/pypsa/6a9e8479-7367-4c25-b9d6-ff0241ed0c32n%40googlegroups.com
> <https://groups.google.com/d/msgid/pypsa/6a9e8479-7367-4c25-b9d6-ff0241ed0c32n%40googlegroups.com?utm_medium=email&utm_source=footer>.
--
Tom Brown (he/him)
Professor of Digital Transformation in Energy Systems
Institute of Energy Technology
Technische Universität Berlin
Group website: https://tub-ensys.github.io/
Personal website: https://nworbmot.org/
Visitor Address:
Einsteinufer 25 (TA 8)
10587 Berlin
We'll try and fix those bugs in the documentation over the next few days
- some of it has organically grown and needs correcting.
Best wishes,
Tom
On 29/06/2022 16:57, Julio Pascual Miqueleiz wrote:
> Externe E-Mail: Oeffnen Sie Anhaenge oder Links nur, wenn Sie der Quelle vertrauen.
> External E-Mail: Be cautious before clicking any link or attachment!
>
> Hello:
>
> My name is Julio, I'm a professor at UPNA (Spain) and I am just new to
> PyPSA/PyPSA-Eur. Having wanted to try it for quite a long time I have
> finally found the time to do it.
>
> With this first message I wanted to, firstly, thank Tom Brown, Fabian
> Neumann and all other developers for this amazing software, the clear
> documentation and the tutorials.
>
> Also, I would like to share my first impressions, typos (or not) that
> I've found in the documentation and workarounds that I had to use when
> running the basic tutorials. This would be my small contribution after
> my first days of use and I hope it is useful for someone. I must say
> that not only I'm new to PyPSA but also to Python so, sorry in advance
> if something is really obvious or doesn't make sense. Here I go:
>
> PyPSA documentation
>
> *Quick-start* (https://pypsa.readthedocs.io/en/latest/quick_start.html
> Hello:
>
> My name is Julio, I'm a professor at UPNA (Spain) and I am just new to
> PyPSA/PyPSA-Eur. Having wanted to try it for quite a long time I have
> finally found the time to do it.
>
> With this first message I wanted to, firstly, thank Tom Brown, Fabian
> Neumann and all other developers for this amazing software, the clear
> documentation and the tutorials.
>
> Also, I would like to share my first impressions, typos (or not) that
> I've found in the documentation and workarounds that I had to use when
> running the basic tutorials. This would be my small contribution after
> my first days of use and I hope it is useful for someone. I must say
> that not only I'm new to PyPSA but also to Python so, sorry in advance
> if something is really obvious or doesn't make sense. Here I go:
>
> PyPSA documentation
>
> <https://pypsa.readthedocs.io/en/latest/quick_start.html>):
>
> I think that last paragraph of Quick Start should say ‘reactive power’
> instead of ‘inactive power’.
>
> *Meshed AC_DC*
> I think that last paragraph of Quick Start should say ‘reactive power’
> instead of ‘inactive power’.
>
> (https://pypsa.readthedocs.io/en/latest/examples/ac-dc-lopf.html
> <https://pypsa.readthedocs.io/en/latest/examples/ac-dc-lopf.html>):
>
> Example did not work as it is. Error at ‘network.lopf();’. Worked with
> ‘network.lopf(pyomo=False);’.
>
> PyPSA-Eur documentation
>
> *Tutorial *(https://pypsa-eur.readthedocs.io/en/latest/tutorial.html#
> Example did not work as it is. Error at ‘network.lopf();’. Worked with
> ‘network.lopf(pyomo=False);’.
>
> PyPSA-Eur documentation
>
> <https://pypsa-eur.readthedocs.io/en/latest/tutorial.html#>):
>
> Tried the tutorial but failed on first try as ipotp could not be found
> when running the sanakemake. After several attempts for fixing this
> issue, what finally worked was to downgrade ipopt to 3.11.1.
>
> *Subsection ‘How to customise PyPSA-Eur?’*: seems like the last two code
> Tried the tutorial but failed on first try as ipotp could not be found
> when running the sanakemake. After several attempts for fixing this
> issue, what finally worked was to downgrade ipopt to 3.11.1.
>
> boxes are not related to the explanatory text right before them (those
> talking about the selection of ERA-5 or SARAH-2 and the selection of the
> optimizer).
>
> *Subsection ‘How to analyse solved networks?*’: the link to PyPSA
> talking about the selection of ERA-5 or SARAH-2 and the selection of the
> optimizer).
>
> examples does not work.
>
> *Wildcards *(https://pypsa-eur.readthedocs.io/en/latest/wildcards.html
> <https://pypsa-eur.readthedocs.io/en/latest/wildcards.html>):
>
> It would be useful to have a template of the snakemake code line as
> first thing in this page. Something like what appears in the Tutorial
> subsection ‘How to use the snakemake rules?’
> (*elec_s{simpl}_{clusters}_ec_l{ll}_{opts}.nc*). Even though, not all
> It would be useful to have a template of the snakemake code line as
> first thing in this page. Something like what appears in the Tutorial
> subsection ‘How to use the snakemake rules?’
> wildcards are shown in that example; wildcards after {opts} seem to be
> missing, i.e., {country}, {cutout}, {technology}, {attr} and {ext},
> although maybe they are not intended to be used the way I think...
>
> *Configuration*
> missing, i.e., {country}, {cutout}, {technology}, {attr} and {ext},
> although maybe they are not intended to be used the way I think...
>
> (https://pypsa-eur.readthedocs.io/en/latest/configuration.html
> <https://pypsa-eur.readthedocs.io/en/latest/configuration.html>):
>
> snapshots > [closed] > Description: It says ‘Make the time interval
> closed to the [left], [right], or both sides [None]’. I may be wrong but
> it seems like [None] means *open* on both sides.
>
> *Preparing
> snapshots > [closed] > Description: It says ‘Make the time interval
> closed to the [left], [right], or both sides [None]’. I may be wrong but
> it seems like [None] means *open* on both sides.
>
> Networks*(https://pypsa-eur.readthedocs.io/en/latest/preparation.html
> <https://pypsa-eur.readthedocs.io/en/latest/preparation.html>):
>
> Retrieve_databundle. I think where it says 19 MB should say 197 MB?
>
> Finally, a more general comment. I tried to analyse the resulting
> networks using Spyder in the pypsa-eur environment but Spyder could not
> be opened. Seems like a problem with jinja2. I realised that in the base
> environment, where Spyder works for me, the version of jinja2 is 2.11.3
> but in the pypsa-eur environment is 3.1.2. I unsuccessfully tried to
> downgrade jinja2. So I couldn’t solve it but, in any case, I can analyse
> the network under other environments or using other Python IDEs.
>
> As I said, I am just starting (only 3 days since I installed it) so I
> guess I will be around here for the next days/weeks/months.
>
> Once again, thank you all, and see you around,
>
> Julio
>
>
>
>
> --
> Retrieve_databundle. I think where it says 19 MB should say 197 MB?
>
> Finally, a more general comment. I tried to analyse the resulting
> networks using Spyder in the pypsa-eur environment but Spyder could not
> be opened. Seems like a problem with jinja2. I realised that in the base
> environment, where Spyder works for me, the version of jinja2 is 2.11.3
> but in the pypsa-eur environment is 3.1.2. I unsuccessfully tried to
> downgrade jinja2. So I couldn’t solve it but, in any case, I can analyse
> the network under other environments or using other Python IDEs.
>
> As I said, I am just starting (only 3 days since I installed it) so I
> guess I will be around here for the next days/weeks/months.
>
> Once again, thank you all, and see you around,
>
> Julio
>
>
>
>
> You received this message because you are subscribed to the Google
> Groups "pypsa" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to pypsa+un...@googlegroups.com
> <mailto:pypsa+un...@googlegroups.com>.
> To view this discussion on the web, visit
> https://groups.google.com/d/msgid/pypsa/6a9e8479-7367-4c25-b9d6-ff0241ed0c32n%40googlegroups.com
> <https://groups.google.com/d/msgid/pypsa/6a9e8479-7367-4c25-b9d6-ff0241ed0c32n%40googlegroups.com?utm_medium=email&utm_source=footer>.
--
Tom Brown (he/him)
Professor of Digital Transformation in Energy Systems
Institute of Energy Technology
Technische Universität Berlin
Group website: https://tub-ensys.github.io/
Personal website: https://nworbmot.org/
Visitor Address:
Einsteinufer 25 (TA 8)
10587 Berlin
Fabian Neumann
Jun 30, 2022, 3:06:13 AM6/30/22
to py...@googlegroups.com
Hi Julio,
thanks for your feedback and suggestions to improve the documentation.
I have implemented those. If you have further suggestion, you can also
try adding them yourself. This would work via pull requests:
https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request
Best wishes,
Fabian N
On 29.06.22 16:57, Julio Pascual Miqueleiz wrote:
> Externe E-Mail: Oeffnen Sie Anhaenge oder Links nur, wenn Sie der Quelle vertrauen.
> External E-Mail: Be cautious before clicking any link or attachment!
>
> examples does not work.
>
Fabian Neumann (he/him)
Postdoctoral Researcher
Department of Digital Transformation in Energy Systems
Zoom: https://tu-berlin.zoom.us/my/fneum
Schedule Meeting: https://calendly.com/fneum
Visitor Address:
Einsteinufer 25 (TA 8)
10587 Berlin
My working hours may not be your working hours. Do not feel pressure to
reply to this email outside your working hours.
thanks for your feedback and suggestions to improve the documentation.
I have implemented those. If you have further suggestion, you can also
try adding them yourself. This would work via pull requests:
https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request
Best wishes,
Fabian N
On 29.06.22 16:57, Julio Pascual Miqueleiz wrote:
> Externe E-Mail: Oeffnen Sie Anhaenge oder Links nur, wenn Sie der Quelle vertrauen.
> External E-Mail: Be cautious before clicking any link or attachment!
>
> Hello:
>
> My name is Julio, I'm a professor at UPNA (Spain) and I am just new to
> PyPSA/PyPSA-Eur. Having wanted to try it for quite a long time I have
> finally found the time to do it.
>
> With this first message I wanted to, firstly, thank Tom Brown, Fabian
> Neumann and all other developers for this amazing software, the clear
> documentation and the tutorials.
>
> Also, I would like to share my first impressions, typos (or not) that
> I've found in the documentation and workarounds that I had to use when
> running the basic tutorials. This would be my small contribution after
> my first days of use and I hope it is useful for someone. I must say
> that not only I'm new to PyPSA but also to Python so, sorry in advance
> if something is really obvious or doesn't make sense. Here I go:
>
> PyPSA documentation
>
>
> My name is Julio, I'm a professor at UPNA (Spain) and I am just new to
> PyPSA/PyPSA-Eur. Having wanted to try it for quite a long time I have
> finally found the time to do it.
>
> With this first message I wanted to, firstly, thank Tom Brown, Fabian
> Neumann and all other developers for this amazing software, the clear
> documentation and the tutorials.
>
> Also, I would like to share my first impressions, typos (or not) that
> I've found in the documentation and workarounds that I had to use when
> running the basic tutorials. This would be my small contribution after
> my first days of use and I hope it is useful for someone. I must say
> that not only I'm new to PyPSA but also to Python so, sorry in advance
> if something is really obvious or doesn't make sense. Here I go:
>
> PyPSA documentation
>
> *Quick-start* (https://pypsa.readthedocs.io/en/latest/quick_start.html
> <https://pypsa.readthedocs.io/en/latest/quick_start.html>):
>
> <https://pypsa.readthedocs.io/en/latest/quick_start.html>):
>
> I think that last paragraph of Quick Start should say ‘reactive power’
> instead of ‘inactive power’.
>
> instead of ‘inactive power’.
>
> *Meshed AC_DC*
> (https://pypsa.readthedocs.io/en/latest/examples/ac-dc-lopf.html
> <https://pypsa.readthedocs.io/en/latest/examples/ac-dc-lopf.html>):
>
> (https://pypsa.readthedocs.io/en/latest/examples/ac-dc-lopf.html
> <https://pypsa.readthedocs.io/en/latest/examples/ac-dc-lopf.html>):
>
> Example did not work as it is. Error at ‘network.lopf();’. Worked with
> ‘network.lopf(pyomo=False);’.
>
> PyPSA-Eur documentation
>
> ‘network.lopf(pyomo=False);’.
>
> PyPSA-Eur documentation
>
> *Tutorial *(https://pypsa-eur.readthedocs.io/en/latest/tutorial.html#
> <https://pypsa-eur.readthedocs.io/en/latest/tutorial.html#>):
>
> <https://pypsa-eur.readthedocs.io/en/latest/tutorial.html#>):
>
> Tried the tutorial but failed on first try as ipotp could not be found
> when running the sanakemake. After several attempts for fixing this
> issue, what finally worked was to downgrade ipopt to 3.11.1.
>
> *Subsection ‘How to customise PyPSA-Eur?’*: seems like the last two code
> when running the sanakemake. After several attempts for fixing this
> issue, what finally worked was to downgrade ipopt to 3.11.1.
>
> boxes are not related to the explanatory text right before them (those
> talking about the selection of ERA-5 or SARAH-2 and the selection of the
> optimizer).
>
> *Subsection ‘How to analyse solved networks?*’: the link to PyPSA
> talking about the selection of ERA-5 or SARAH-2 and the selection of the
> optimizer).
>
> examples does not work.
>
> *Wildcards *(https://pypsa-eur.readthedocs.io/en/latest/wildcards.html
> <https://pypsa-eur.readthedocs.io/en/latest/wildcards.html>):
>
> <https://pypsa-eur.readthedocs.io/en/latest/wildcards.html>):
>
> It would be useful to have a template of the snakemake code line as
> first thing in this page. Something like what appears in the Tutorial
> subsection ‘How to use the snakemake rules?’
> (*elec_s{simpl}_{clusters}_ec_l{ll}_{opts}.nc*). Even though, not all
> first thing in this page. Something like what appears in the Tutorial
> subsection ‘How to use the snakemake rules?’
> wildcards are shown in that example; wildcards after {opts} seem to be
> missing, i.e., {country}, {cutout}, {technology}, {attr} and {ext},
> although maybe they are not intended to be used the way I think...
>
> missing, i.e., {country}, {cutout}, {technology}, {attr} and {ext},
> although maybe they are not intended to be used the way I think...
>
> *Configuration*
> (https://pypsa-eur.readthedocs.io/en/latest/configuration.html
> <https://pypsa-eur.readthedocs.io/en/latest/configuration.html>):
>
> (https://pypsa-eur.readthedocs.io/en/latest/configuration.html
> <https://pypsa-eur.readthedocs.io/en/latest/configuration.html>):
>
> snapshots > [closed] > Description: It says ‘Make the time interval
> closed to the [left], [right], or both sides [None]’. I may be wrong but
> it seems like [None] means *open* on both sides.
>
> closed to the [left], [right], or both sides [None]’. I may be wrong but
> it seems like [None] means *open* on both sides.
>
> *Preparing
> Networks*(https://pypsa-eur.readthedocs.io/en/latest/preparation.html
> <https://pypsa-eur.readthedocs.io/en/latest/preparation.html>):
>
> Networks*(https://pypsa-eur.readthedocs.io/en/latest/preparation.html
> <https://pypsa-eur.readthedocs.io/en/latest/preparation.html>):
>
> Retrieve_databundle. I think where it says 19 MB should say 197 MB?
>
> Finally, a more general comment. I tried to analyse the resulting
> networks using Spyder in the pypsa-eur environment but Spyder could not
> be opened. Seems like a problem with jinja2. I realised that in the base
> environment, where Spyder works for me, the version of jinja2 is 2.11.3
> but in the pypsa-eur environment is 3.1.2. I unsuccessfully tried to
> downgrade jinja2. So I couldn’t solve it but, in any case, I can analyse
> the network under other environments or using other Python IDEs.
>
> As I said, I am just starting (only 3 days since I installed it) so I
> guess I will be around here for the next days/weeks/months.
>
> Once again, thank you all, and see you around,
>
> Julio
>
>
>
>
>
> Finally, a more general comment. I tried to analyse the resulting
> networks using Spyder in the pypsa-eur environment but Spyder could not
> be opened. Seems like a problem with jinja2. I realised that in the base
> environment, where Spyder works for me, the version of jinja2 is 2.11.3
> but in the pypsa-eur environment is 3.1.2. I unsuccessfully tried to
> downgrade jinja2. So I couldn’t solve it but, in any case, I can analyse
> the network under other environments or using other Python IDEs.
>
> As I said, I am just starting (only 3 days since I installed it) so I
> guess I will be around here for the next days/weeks/months.
>
> Once again, thank you all, and see you around,
>
> Julio
>
>
>
>
> --
> You received this message because you are subscribed to the Google
> Groups "pypsa" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to pypsa+un...@googlegroups.com
> <mailto:pypsa+un...@googlegroups.com>.
> To view this discussion on the web, visit
> https://groups.google.com/d/msgid/pypsa/6a9e8479-7367-4c25-b9d6-ff0241ed0c32n%40googlegroups.com
> <https://groups.google.com/d/msgid/pypsa/6a9e8479-7367-4c25-b9d6-ff0241ed0c32n%40googlegroups.com?utm_medium=email&utm_source=footer>.
--
Dr.-Ing.
> You received this message because you are subscribed to the Google
> Groups "pypsa" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to pypsa+un...@googlegroups.com
> <mailto:pypsa+un...@googlegroups.com>.
> To view this discussion on the web, visit
> https://groups.google.com/d/msgid/pypsa/6a9e8479-7367-4c25-b9d6-ff0241ed0c32n%40googlegroups.com
> <https://groups.google.com/d/msgid/pypsa/6a9e8479-7367-4c25-b9d6-ff0241ed0c32n%40googlegroups.com?utm_medium=email&utm_source=footer>.
--
Fabian Neumann (he/him)
Postdoctoral Researcher
Department of Digital Transformation in Energy Systems
Institute of Energy Technology
Technische Universität Berlin
Group website: https://tub-ensys.github.io
Personal website: https://neumann.fyi
Technische Universität Berlin
Group website: https://tub-ensys.github.io
Zoom: https://tu-berlin.zoom.us/my/fneum
Schedule Meeting: https://calendly.com/fneum
Visitor Address:
Einsteinufer 25 (TA 8)
10587 Berlin
reply to this email outside your working hours.
Julio Pascual Miqueleiz
Jun 30, 2022, 5:44:10 AM6/30/22
to pypsa
Thank you, Tom and Fabian, for you very fast response.
I can see at the Pull requests section in GitHub that changes have been made. Note however that some of the changes do not appear yet on the readthedocs website but I guess it's just a matter of time.
Regarding the use of Pull request, I didn't use this channel because at that time I thought it was only meant for the software itself, not its documentation. Now that I'm aware I will suggest further changes through GitHub.
Thank you very much,
Julio
Reply all
Reply to author
Forward
0 new messages