start course with optimisation section and finish with profiling tools

Author: msarkis-icr

config.yaml

@@ -11,7 +11,7 @@
 carpentry: 'incubator'
 
 # Overall title for pages.
-title: 'Performance Profiling & Optimisation (Python)'
+title: 'Python Optimisation and Performance Profiling'
 
 # Date the lesson was created (YYYY-MM-DD, this is empty by default)
 created: 2024-02-01~ # FIXME
@@ -27,13 +27,13 @@ life_cycle: 'alpha'
 license: 'CC-BY 4.0'
 
 # Link to the source repository for this lesson
-source: 'https://github.com/RSE-Sheffield/pando-python'
+source: 'https://github.com/ICR-RSE-Group/carpentry-pando-python'
 
 # Default branch of your lesson
 branch: 'main'
 
 # Who to contact if there are any issues
-contact: 'robert.chisholm@sheffield.ac.uk'
+contact: 'mira.sarkis@icr.ac.uk'
 
 # Navigation ------------------------------------------------
 #
@@ -59,18 +59,17 @@ contact: '[email protected]'
 
 # Order of episodes in your lesson
 episodes: 
-- profiling-introduction.md
-- profiling-functions.md
-- short-break1.md
-- profiling-lines.md
-- profiling-conclusion.md
 - optimisation-introduction.md
 - optimisation-data-structures-algorithms.md
-- long-break1.md
 - optimisation-minimise-python.md
 - optimisation-use-latest.md
 - optimisation-memory.md
 - optimisation-conclusion.md
+- long-break1.md
+- profiling-introduction.md
+- profiling-functions.md
+- profiling-lines.md
+- profiling-conclusion.md
 
 # Information for Learners
 learners: 
@@ -92,4 +91,4 @@ profiles:
 # sandpaper and varnish versions) should live
 
 varnish: RSE-Sheffield/uos-varnish@main
-url: 'https://rse.shef.ac.uk/pando-python'
+url: 'https://icr-rse-group.github.io/carpentry-pando-python'

episodes/profiling-introduction.md

@@ -41,7 +41,7 @@ Increasingly, particularly with relation to HPC, attention is being paid to the
 
 Profiling is most relevant to working code, when you have reached a stage that the code works and are considering deploying it.
 
-Any code that will run for more than a few minutes over it's lifetime, that isn't a quick one-shot script can benefit from profiling.
+Any code that will run for more than a few minutes over its lifetime, that isn't a quick one-shot script can benefit from profiling.
 
 Profiling should be a relatively quick and inexpensive process. If there are no significant bottlenecks in your code you can quickly be confident that your code is reasonably optimised. If you do identify a concerning bottleneck, further work to optimise your code and reduce the bottleneck could see significant improvements to the performance of your code and hence productivity.
 

index.md

@@ -3,18 +3,17 @@ site: sandpaper::sandpaper_site
 ---
 
 <!--
-![Welcome to Performance Profiling & Optimisation (Python) Training!
+![Welcome to Python Optimisation and Performance Profiling Training!
 ](episodes/fig/pando-python-hex-sticker.png){
-alt='Performance Profiling & Optimisation (Python) Training'
+alt='Python Optimisation and Performance Profiling Training'
 style='padding: 2%'}
 -->
 
-**Welcome to Performance Profiling & Optimisation (Python) Training!**
+**Welcome to Python Optimisation and Performance Profiling Training!**
 
 The training curriculum for this course is designed for researchers that are writing Python and lack formal computer science training. The curriculum covers how to assess where time is being spent during execution of a Python program, it also provides a high level understanding of how code executes and how this maps to the limiting factors of performance and good practice.
 
-If you are now comfortable using Python, this course may be of interest to supplement and advance your programming knowledge. This course is particularly relevant if you are writing research code and desire greater confidence that your code is both performant and suitable for publication.
-
+If you are now comfortable using Python, this course may be of interest to supplement and advance your programming knowledge. This course is particularly relevant if you are writing from scratch or re-using and existing research code and would desire a greater confidence that your code is both performant and suitable for publication. 
 This is an all-day course, however it normally finishes by early afternoon.
 
 If you would like to register to take the course, check the [registration information](learners/registration.md).
@@ -34,20 +33,20 @@ If you would like to register to take the course, check the [registration inform
 <!-- Evaluation tool: https://web.cs.manchester.ac.uk/iloadvisor/ -->
 After attending this training, participants will be able to:
 
-- identify the most expensive functions and lines of code using `cprofile` and `line_profiler`.
-- evaluate code to determine the limiting factors of it's performance.
 - recognise and implement optimisations for common limiting factors of performance.
+- identify the most expensive functions and lines of code using `cprofile` and `line_profiler`.
+- evaluate code to determine the limiting factors of its performance.
 
 ::::::::::::::::::::::::::::::::::::::::::  prereq
 
 ## Prerequisites
 
-Before joining Performance Profiling & Optimisation (Python) Training, participants should be able to:
+Before joining Python Optimisation and Performance Profiling Training, participants should be able to:
 
 - implement basic algorithms in Python.
 - follow the control flow of Python code, and dry run the execution in their head or on paper.
 
-See the [Research Computing Training Hub](https://sites.google.com/sheffield.ac.uk/research-training/research-training) for other courses to help with learning these skills.
+See the [Python novice carpentry ](https://icr-rse-group.github.io/carpentry-python-novice/instructor/index.html) for another course to help with learning these skills.
 <!-- TODO: could make a dedicated page (like https://carpentries.github.io/lesson-development-training/markdown-github-primer.html) that highlights specific courses/resources. -->
 
 ::::::::::::::::::::::::::::::::::::::::::::::::::