Merge pull request #1594 from bug-or-feature/feature-1593-new-org

update project url for new org

Author: bug-or-feature

CHANGELOG.md

@@ -13,7 +13,7 @@
 
 - *NO LONGER REQUIRES ARCTIC* Time series data is stored in parquet, install pyarrow
 - But does require newer versions of pandas and python, see requirements.txt
-- See the discussion [here](https://github.com/robcarver17/pysystemtrade/discussions/1290) to see how to switch from arctic to parquet
+- See the discussion [here](https://github.com/pst-group/pysystemtrade/discussions/1290) to see how to switch from arctic to parquet
 - added long only constraint to dynamic optimisation
 - various bugs fixed
 
@@ -77,20 +77,20 @@ Other:
 
 ## Version 1.50
 
-- Added optional code to run price collection throughout the day, see [announcement](https://github.com/robcarver17/pysystemtrade/discussions/961)
+- Added optional code to run price collection throughout the day, see [announcement](https://github.com/pst-group/pysystemtrade/discussions/961)
 - Added ability to pass arguments to methods through control_config.yaml
 - Added regions to instrument.csv configuration; use interactive_controls, option 5, option 52 to apply
 
 ## Version 1.48
 
 - Added new run_ processes, breaking out FX, update sampled contracts, and update multiple/adjusted prices from daily price updates. You will need to update your crontab and control_config.yaml, see **discussion here**
 - Refactoring syscore
-- Changed handling of expensive instruments, [see this discussion](https://github.com/robcarver17/pysystemtrade/discussions/938)
-- Added requirement for BLACK [see this discussion](https://github.com/robcarver17/pysystemtrade/discussions/921)
-- Roll report clean up format [discussed here](https://github.com/robcarver17/pysystemtrade/discussions/864)
+- Changed handling of expensive instruments, [see this discussion](https://github.com/pst-group/pysystemtrade/discussions/938)
+- Added requirement for BLACK [see this discussion](https://github.com/pst-group/pysystemtrade/discussions/921)
+- Roll report clean up format [discussed here](https://github.com/pst-group/pysystemtrade/discussions/864)
 - Gradual removal of missing_data, missing_contract type objects and replace with exceptions
-- Algos won't be allocated just before day end [discussed here](https://github.com/robcarver17/pysystemtrade/discussions/853)
-- Timezones can now be manually configured [discussed here](https://github.com/robcarver17/pysystemtrade/discussions/845)
+- Algos won't be allocated just before day end [discussed here](https://github.com/pst-group/pysystemtrade/discussions/853)
+- Timezones can now be manually configured [discussed here](https://github.com/pst-group/pysystemtrade/discussions/845)
 - Auto copying of instrument config data between db and csv
 - Utility to cross check IB configuration multipliers
 - Utility to delete instrument data
@@ -115,9 +115,9 @@ Other:
 - "Market movers" report added
 - Nicer functionality to get dates into reports interactively
 - Added volume limits to auto fill position limits
-- Fixed cost calculation for dynamic optimisation (see [discussion](https://github.com/robcarver17/pysystemtrade/discussions/647))
-- Private config now always pulled in, even for backtests (see [discussion](https://github.com/robcarver17/pysystemtrade/discussions/633))
-- Improved price cleaning (see [discussion](https://github.com/robcarver17/pysystemtrade/discussions/646))
+- Fixed cost calculation for dynamic optimisation (see [discussion](https://github.com/pst-group/pysystemtrade/discussions/647))
+- Private config now always pulled in, even for backtests (see [discussion](https://github.com/pst-group/pysystemtrade/discussions/633))
+- Improved price cleaning (see [discussion](https://github.com/pst-group/pysystemtrade/discussions/646))
 
 ## Version 1.31 (didn't seem to do any notes for 1.30)
 
@@ -466,7 +466,7 @@ Moved most examples except core to separate git [here](https://github.com/robcar
 
 ## Version 0.12.0
 
-* Capital correction now works. New methods: system.accounts.capital_multiplier, system.accounts.portfolio_with_multiplier, system.portfolio.get_actual_positon, system.portfolio.get_actual_buffers_with_position, system.accounts.get_buffered_position_with_multiplier. See this [blog post](https://qoppac.blogspot.com/2016/06/capital-correction-pysystemtrade.html) and [the guide](https://github.com/robcarver17/pysystemtrade/blob/master/docs/userguide.md#capcorrection)
+* Capital correction now works. New methods: system.accounts.capital_multiplier, system.accounts.portfolio_with_multiplier, system.portfolio.get_actual_positon, system.portfolio.get_actual_buffers_with_position, system.accounts.get_buffered_position_with_multiplier. See this [blog post](https://qoppac.blogspot.com/2016/06/capital-correction-pysystemtrade.html) and [the guide](https://github.com/pst-group/pysystemtrade/blob/master/docs/backtesting.md#capital-correction---varying-capital)
 
 
 ## Version 0.11.2

CONTRIBUTING.md

@@ -13,7 +13,7 @@ For large changes, or new feature requests - please start an **Ideas** discussio
 > Credit to the [QuantConnect Lean project](https://github.com/QuantConnect/Lean), where most of these instructions originated
 
 * Set up a [GitHub](https://github.com/) account
-* [Fork](https://help.github.com/articles/fork-a-repo/) the [repository](https://github.com/robcarver17/pysystemtrade) of the project
+* [Fork](https://help.github.com/articles/fork-a-repo/) the [repository](https://github.com/pst-group/pysystemtrade) of the project
 * Clone your fork locally
 
 ```bash
@@ -24,7 +24,7 @@ $ git clone https://github.com/<your_username>/pysystemtrade.git
 
 ```bash
 $ cd pysystemtrade
-$ git remote add upstream https://github.com/robcarver17/pysystemtrade.git
+$ git remote add upstream https://github.com/pst-group/pysystemtrade.git
 ```
 
 The *upstream* remote links your fork of the project with the original
@@ -46,7 +46,7 @@ If you are not familiar with git branches, please read this [guide](https://www.
 
 The following names will be used to differentiate between the different repositories:
 
-* **upstream** - The 'official' pysystemtrade [repository](https://github.com/robcarver17/pysystemtrade.git) (what is on Rob's GitHub account)
+* **upstream** - The 'official' pysystemtrade [repository](https://github.com/pst-group/pysystemtrade.git) (what is on the pst-group GitHub account)
 * **origin** - Your fork of the official repository on GitHub (what is on your GitHub account)
 * **local** - This will be your local clone of **origin** (what is on your computer)
 
@@ -177,7 +177,7 @@ Or, configure your local git install to automatically check and fix your code as
 
 ### Black version
 
-Black needs to be consistent between the version running in the CI build and your local environment. To check the currently used version, see the `[tool.black]` section of the project [TOML file](https://github.com/robcarver17/pysystemtrade/blob/develop/pyproject.toml)
+Black needs to be consistent between the version running in the CI build and your local environment. To check the currently used version, see the `[tool.black]` section of the project [TOML file](https://github.com/pst-group/pysystemtrade/blob/develop/pyproject.toml)
 
 ## General code guidelines (INCOMPLETE)
 
@@ -196,7 +196,7 @@ In general, we try and follow the original texts: [PEP 8](https://peps.python.or
 
 - For classes, I prefer mixedCase to CamelCase, but single word names should always be Camels.
 - Common methods are `get`, `calculate`, `read`, `write`.
-- There is a specific procedure for naming objects which form part of the data heirarchy, see [here](https://github.com/robcarver17/pysystemtrade/blob/master/docs/data.md#part-2-overview-of-futures-data-in-pysystemtrade). If this is not followed, then the [automated abstraction of data inside Data 'blob' instances](https://github.com/robcarver17/pysystemtrade/blob/master/docs/data.md#data-blobs) won't work.
+- There is a specific procedure for naming objects which form part of the data heirarchy, see [here](https://github.com/pst-group/pysystemtrade/blob/master/docs/data.md#part-2-overview-of-futures-data-in-pysystemtrade). If this is not followed, then the [automated abstraction of data inside Data 'blob' instances](https://github.com/pst-group/pysystemtrade/blob/master/docs/data.md#data-blobs) won't work.
 - Although arguably redundant, I am a fan of describing eg objects that inherit from dicts with a dict_ prefix. This gives hints as to how they behave without having to look at their code.
 
 

README.md

@@ -44,7 +44,7 @@ This package isn't hosted on pypi.org. So to get the code the easiest way is to
 
 ```
 # clone the repo to your local filesystem
-$ git clone https://github.com/robcarver17/pysystemtrade.git
+$ git clone https://github.com/pst-group/pysystemtrade.git
 
 # navigate to the project directory
 $ cd pysystemtrade
@@ -60,7 +60,7 @@ There is a more complete installation guide [here](docs/installation.md)
 
 ### A note on support
 
-This is an open source project, designed for people who are already comfortable using and writing python code, are capable of installing the dependencies, and who want a head start on implementing a system of their own.  If you need a higher level of support then you are better off with another project. The most efficient way of getting support is by [opening an issue on github](https://github.com/robcarver17/pysystemtrade/issues/new). If you discover a bug please include:
+This is an open source project, designed for people who are already comfortable using and writing python code, are capable of installing the dependencies, and who want a head start on implementing a system of their own.  If you need a higher level of support then you are better off with another project. The most efficient way of getting support is by [opening an issue on github](https://github.com/pst-group/pysystemtrade/issues/new). If you discover a bug please include:
 
 - The full script that produces the error, including all `import` statements, or if it's a standard example file a pointer to the file. Ideally this should be a "minimal example" - the shortest possible script that produces the problem.
 - Versions of any necessary libraries you have installed

docs/backtesting.md

@@ -901,7 +901,7 @@ print(system.accounts.portfolio().sharpe())
 
 #### Arctic
 
-Early versions of this project used [Arctic](https://github.com/manahl/arctic) for storing time series data. Since November 2023, Parquet is the default. See [the reasoning behind the change](https://github.com/robcarver17/pysystemtrade/discussions/466), [switchover instructions](https://github.com/robcarver17/pysystemtrade/discussions/1290), and [required scheduling config changes](https://github.com/robcarver17/pysystemtrade/discussions/1291).
+Early versions of this project used [Arctic](https://github.com/manahl/arctic) for storing time series data. Since November 2023, Parquet is the default. See [the reasoning behind the change](https://github.com/pst-group/pysystemtrade/discussions/466), [switchover instructions](https://github.com/pst-group/pysystemtrade/discussions/1290), and [required scheduling config changes](https://github.com/pst-group/pysystemtrade/discussions/1291).
 
 The [original Arctic project](https://github.com/man-group/arctic) is no longer maintained - development has moved to [ArcticDB](https://github.com/man-group/ArcticDB)
 
@@ -3443,7 +3443,7 @@ I've included a smoothing function, otherwise jumps in the multiplier will cause
 
 ## Specifying weights as hierarchy
 
-It is possible to specify instrument and forecast weights as a hierarchical config. This has the advantage that the high-level characteristics of a trading strategy can be maintained, even when rules (or instruments) are excluded due to costs. Read more [here](https://github.com/robcarver17/pysystemtrade/discussions/1160). See below for example config snippets
+It is possible to specify instrument and forecast weights as a hierarchical config. This has the advantage that the high-level characteristics of a trading strategy can be maintained, even when rules (or instruments) are excluded due to costs. Read more [here](https://github.com/pst-group/pysystemtrade/discussions/1160). See below for example config snippets
 
 ### Hierarchical forecast weight example
 

docs/data.md

@@ -126,7 +126,7 @@ Hence, there are five possible use cases:
 Because of this it's possible at (almost) every stage to store data in either CSV or databases (the exception are roll calendars, which only live in CSV format).
 
 ### Note on outdated shipped CSV data
-The CSV multiple and adjusted files supplied with the project have not been updated since March 2024, when Rob stepped back from the project. You can find an updated (sub)set of files in [this project](https://github.com/bug-or-feature/pst-csv-data). See the [discussion here](https://github.com/robcarver17/pysystemtrade/discussions/1553) 
+The CSV multiple and adjusted files supplied with the project have not been updated since March 2024, when Rob stepped back from the project. You can find an updated (sub)set of files in [this project](https://github.com/bug-or-feature/pst-csv-data). See the [discussion here](https://github.com/pst-group/pysystemtrade/discussions/1553) 
 
 ## Instrument configuration and spread costs
 
@@ -378,7 +378,7 @@ This will also copy adjusted prices, so you can now skip ahead to [creating FX d
 
 ### Updating shipped multiple prices
 
-See [this script](https://github.com/robcarver17/pysystemtrade/blob/develop/sysinit/futures/adhoc/update_provided_multiple_prices.py) 
+See [this script](https://github.com/pst-group/pysystemtrade/blob/develop/sysinit/futures/adhoc/update_provided_multiple_prices.py) 
 
 Assuming that you have an Interactive Brokers account, you might want to update the (stale) data that you have [downloaded from the repo](/docs/backtesting.md#setting-up-mongodb-and-parquet) before [calculating back adjusted prices](#creating-and-storing-back-adjusted-prices). [See this note](#note-on-outdated-shipped-csv-data)
 

docs/installation.md

@@ -15,7 +15,7 @@ git clone https://github.com/<your_git_hub_id>/pysystemtrade.git
 otherwise, you'll want the main repo
 
 ```
-git clone https://github.com/robcarver17/pysystemtrade.git
+git clone https://github.com/pst-group/pysystemtrade.git
 ```
 
 

docs/notebooks/introduction_with_fxdata.ipynb

@@ -13,9 +13,9 @@
    "id": "db9723dc",
    "metadata": {},
    "source": [
-    "This is the trading rule example shown in [the introduction](https://github.com/robcarver17/pysystemtrade/blob/master/docs/introduction.md) but modified to use Interactive Brokers instead of CSV files as data source.  \n",
+    "This is the trading rule example shown in [the introduction](https://github.com/pst-group/pysystemtrade/blob/master/docs/introduction.md) but modified to use Interactive Brokers instead of CSV files as data source.\n",
     "\n",
-    "IB requires a minimum equity and a monthly subscription to provide historical data on future contracts.  This example was modified to use FX prices instead futures to make it runnable with free unfunded paper trading accounts.  Note that Rob [does not recommend trading FX spot data with IB due to their high fees](https://github.com/robcarver17/pysystemtrade/issues/517#issuecomment-1010770678)."
+    "IB requires a minimum equity and a monthly subscription to provide historical data on future contracts.  This example was modified to use FX prices instead futures to make it runnable with free unfunded paper trading accounts.  Note that Rob [does not recommend trading FX spot data with IB due to their high fees](https://github.com/pst-group/pysystemtrade/issues/517#issuecomment-1010770678)."
    ]
   },
   {

docs/production.md

@@ -2604,7 +2604,7 @@ The scheduler built into pysystemtrade does not launch processes (this is still
 
 Processes still need to be launched every day, since the pysystemtrade scheduler doesn't do that. However, their start time isn't critical, since separate start times can be configured in YAML files (more of that below).
 
-Because I use cron myself, there are is a [cron tab included in pysystemtrade](https://github.com/robcarver17/pysystemtrade/blob/master/sysproduction/linux/crontab).
+Because I use cron myself, there are is a [cron tab included in pysystemtrade](https://github.com/pst-group/pysystemtrade/blob/master/sysproduction/linux/crontab).
 
 Useful things to note about the crontab:
 

pyproject.toml

@@ -8,6 +8,9 @@ version = "1.8.2"
 authors = [
   { name="Robert Carver", email="rob@systematicmoney.org" },
 ]
+maintainers = [
+  { name="Andy Geach", email="andy@bugorfeature.net" },
+]
 description = "Systematic futures trading in Python"
 readme = "README.md"
 license = {file = "LICENSE"}
@@ -36,8 +39,8 @@ arctic = ["arctic @ git+https://github.com/man-group/arctic.git"]
 dev = ["pytest>6.2", "black==23.11.0"]
 
 [project.urls]
-"Homepage" = "https://github.com/robcarver17/pysystemtrade"
-"Bug Tracker" = "https://github.com/robcarver17/pysystemtrade/issues"
+"Homepage" = "https://github.com/pst-group/pysystemtrade"
+"Bug Tracker" = "https://github.com/pst-group/pysystemtrade/issues"
 
 [tool.setuptools.packages]
 find = {}