pythonSCHED 1.28.3
Python extension of NRAO's VLBI scheduling program SCHED (see http://www.aoc.nrao.edu/~cwalker/sched/)
Requires Python: <3.12,>=3.6

# pySCHED



**pySCHED** is a program for planning and scheduling very long baseline interferometry (VLBI) observations conducted by different networks such as the European VLBI Network (EVN), the Very Long Baseline Array (VLBA), the High Sensitivity Array (HSA), the Global VLBI, the Australian Long Baseline Array (LBA), or the Korean VLBI Network (KVN). **pySCHED** produces the standard files that need to be distributed to the different telescopes and correlators for VLBI observations and operations.

**pySCHED** is built upon the [NRAO SCHED](http://www.aoc.nrao.edu/~cwalker/sched/) program developed by Craig Walker at NRAO, and adds unique features:

- Central catalog management on GitHub. The version controlled catalogs provide full access to the change history of each catalog file. By default, at startup, **pySCHED** always updates the catalogs; using old/outdated catalogs is no cause for errors anymore. We note that the feature can be switched off if needed (e.g. for multi-epoch observations).
- Full DBBC2 scheduling support, essential for EVN observations.
- Since v1.8.1 **pySCHED** checks for updates upon startup, informing the user of a new(er) version being available.
- The KEYIN file can be a template schedule with executable Python-code in it. This could simplify scheduling standard observations.
- Can generate VEX1 as well as VEX2 output.
- Plotting is now done through Python's `matplotlib` library, making it easier to control/enhance and/or implement different plots.



## Getting started

To learn how to write a scheduling file (`.key`) that can be used to generate the observing files (`.vex` file) with **pySCHED**, you can follow the User Guide at the [EVN Scheduling Page](https://www.evlbi.org/evn-scheduling). This documentaion is focused on observations with the European VLBI Network (EVN). For a more extended documentation on how to write the scheduling files, please take a look at the general [NRAO SCHED User Manual](http://www.aoc.nrao.edu/~cwalker/sched/).

Once the `.key` file is prepared, **pySCHED** can generate the scheduling files. The basic operations can be conducted by running:

```bash
sched.py [-p] -k {keyfile}
```

where the optional parameter `-p`  retrieves the graphical mode in order to be able to make plots about the observation.



## Installation



### Dependecies

- Python (>= 3.6).
- A Fortran compiler.
- NumPy (>= 1.16, < 1.24).
- Setuptools (<60)
- Git.

#### PyQt5 dependencies

**pySCHED** uses PyQt5 for its GUI. Since version 5.12, PyQt5 has external dependencies that are not automatically installed. Many systems have these dependencies installed, see [this discussion page](https://github.com/jive-vlbi/sched/discussions/16) if you see the error message ```Cannot load backend 'Qt5Agg' which requires the 'qt5' interactive framework, as 'headless' is currently running``` for details.

### conda (recommended)

The recommended installation method for **pySCHED** is to use a conda compatible program. There are a few options for conda installers, like [Anaconda](https://www.anaconda.com/download), [Miniconda](https://docs.anaconda.com/miniconda/) and [Miniforge](https://github.com/conda-forge/miniforge). We recommend [Miniforge](https://github.com/conda-forge/miniforge), since it uses the conda-forge channels by default to download packages, which is free to use, while the default channel of the two other options are not free to use in all circumstances. See [this](https://www.anaconda.com/blog/is-conda-free#summarize) blog for further details and links.

After installing your choice of conda, download [this](https://github.com/jive-vlbi/sched/raw/python/pySCHED.yaml) YAML file, which describes a conda environment including all mentioned dependencies and **pySCHED**. To use it:

```bash
conda env create -f pySCHED.yaml
conda activate pySCHED
```

### pip (not recommended)

**pySCHED** requires an older version of both NumPy and setuptools, therefore we do not recommend installing it outside of a dedicated (virtual) environment. 
If you want to install **pySCHED** using `pip`, it can be used directly:

```bash
sudo pip3 install 'numpy<1.24'
sudo pip3 install 'setuptools<60'
sudo pip3 install pythonSCHED
```

`pip3` is included in most python3 installations, otherwise it can be installed with:

```bash
sudo apt-get install python3-pip
```

### Known issues

If you are encountering issues (both during installation or while running) with pySCHED, please check the [Discussions page](https://github.com/jive-vlbi/sched/discussions). We are summarizing here the most-common problems and how to solve them.

## Update

The command to update pySCHED is:

```bash
sudo pip3 install --upgrade pythonSCHED
```

Or when using a conda installation:

```bash
conda activate pySCHED
pip install --upgrade pythonSCHED
```



## Usage

After executing either the `pip` or `conda` installation method, the executable `sched.py` should be available in your `$PATH`.

One of the features of **pySCHED** is that the catalog files will be downloaded/updated on start-up of `sched.py`. This allows for the catalog files to be updated separate from the pySCHED release cycle. The files will be installed in `~/.pysched`. `$SCHED` will be set to this directory in **pySCHED** if not otherwise specified. The process of downloading and updating requires the version control software `git` to be installed and available in the `$PATH`. On most GNU/Linux systems, `git` will be available. If it is not, it can be installed with:

```bash
sudo apt-get install git
```


### Using pySCHED within a SCHED environment

The aforementioned usage can potentially generate some issues when pySCHED runs in an environment where the variable `$SCHED` is set for the NRAO SCHED program. If `$SCHED` is indeed set to the path that points to the NRAO SCHED directory, then pySCHED will read the catalogs under that directory. In this case, pySCHED will not use the most up-to-date catalogs and may fail to schedule experiments requiring the latest updates.

We therefore recommend to unset this variable before running pySCHED (which would then use the default `~/.pysched` directory) or to be sure the catalogs under the `$SCHED` directory are proficient to schedule your experiment.




# Release history

* __v1.2.0 (2019-09-27)__: Merge with SCHED release 11.5.
* __v1.2.1 (2019-10-18)__: Bug fixes for readline and matplotlib version.
* __v1.3.0 (2019-11-19)__: Added SCANEXPS keyword to signal intent in VEX2 files. To make that work, Fortran function leading to calls of SCNDUP are translated to Python.
* __v1.4.0 (2019-12-13)__: Added 'eMERL' value to DAR keyword, to enable eMERLIN out-station automatic IF and BBC assignment.
* __v1.5.0 (2020-02-25)__: Improved error/warning messages.
* __v1.5.1 (2020-03-24)__: Updated the error message for a missing '/'.
* __v1.5.2 (2020-03-26)__: Update version restriction to PyQt version.
* __v1.5.3 (2020-04-02)__: Handle changes made in matplotlib version 3.2.
* __v1.6.0 (2020-05-12)__: Catalog updates for May/June session and plot improvements.
* __v1.7.0 (2020-05-18)__: Include pySCHED version in command line and interactive help text.
* __v1.8.0 (2020-05-19)__: Do a version check on start-up.
* __v1.8.1 (2020-05-20)__: Include README.md in distribution, it is required for installation.
* __v1.8.2 (2020-05-27)__: Fixed update catalog writing to an unopened log file.
* __v1.9.0 (2020-06-09)__: Overhaul of the README.
* __v1.10.0 (2020-06-22)__: SCHED 11.6 merged into pySCHED.
* __v1.11.0 (2020-07-11)__: Add warning message on empty KEYIN input record.
* __v1.12.0 (2020-07-21)__: Runtime improved by about 30%.
* __v1.12.1 (2020-09-10)__: Bug fix, continuous recording warning would trigger too often.
* __v1.13.0 (2020-10-05)__: Allow double bandwidth for eMERLIN if 1 bits sampling is used.
* __v1.13.1 (2020-10-07)__: Bug(s) in exit.c function triggered compiler error. Turned out to be unused code, so removed from compilation list.
* __v1.13.2 (2020-10-14)__: Update code to support matplotlib version 3.3.
* __v1.14.0 (2020-10-23)__: Updated legend layout of uptime plot and added a help button in the plot toolbar.
* __v1.14.1 (2020-11-05)__: pySCHED uses string formatting introduced in python version 3.6. Make this requirement explicit.
* __v1.14.2 (2020-11-06)__: Fortran index was used to index Python array, causing an error when 16 BBCs were used.
* __v1.15.0 (2020-11-23)__: Cleared up confusion about the starting day of time based plots.
* __v1.16.0 (2021-01-12)__: Now compatible with matplotlib 3.3.3 and advertised the GitHub page in the start-up message.
* __v1.16.1 (2021-01-21)__: Bug fix for XY plots.
* __v1.17.0 (2021-03-29)__: Fix deprecations warned for by matplotlib 3.4.
* __v1.18.0 (2021-05-21)__: Updates to plot UI for smaller desktop windows.
* __v1.19.0 (2021-07-09)__: Add polarization comment for frequency channels in VEX file.
* __v1.19.1 (2021-10-19)__: Bug fixes for BITSTREAMS section generation and deprecated functionality in Matplotlib that caused a crash setting axis properties.
* __v1.20.0 (2021-11-01)__: Add option to display slew times in the uptime plot.
* __v1.20.1 (2021-11-04)__: Escape TeX special characters in Matplotlib plots titles and labels, when Matplotlib is configured to use LaTex to display text.
* __v1.21.0 (2021-11-17)__: Fix deprecations warned for by matplotlib 3.5.
* __v1.22.0 (2022-01-14)__: Add 'JIVE-e-VLBI' as possible target correlator.
* __v1.23.0 (2022-04-28)__: This version introduces three changes:
  * Added extra version information to the VEX file.
  * Search for a given setup file in the $SCHED/setups directory, if it does not include a path and is not found in the current directory.
  * Replace deprecated distutils.version.LooseVersion with packaging.version.parse.
* __v1.24.0 (2022-05-13)__: Incorporate EVN SCHED patches for wrap zone into pySCHED.
* __v1.25.0 (2022-09-30)__: Raise the level at which warnings about sources too close to the sun are printed to standard output and make some of the thresholds used configurable.
* __v1.25.1 (2022-10-06)__: Require a newer version of NumPy. In earlier version calling round(numpy.float) would return a float, which caused a problem in string formatting.
* __v1.25.2 (2023-01-11)__: F2py from NumPy version 1.24 creates different data block wrappers, require an earlier version of NumPy for now.
* __v1.25.3 (2023-02-23)__: Matplotlib version 3.7.0 deprecated the attribute legendHandles for legend_handles. This version supports both to suppress the warning message.
* __v1.25.4 (2023-03-29)__: Fix a bug in the setup script NumPy version specification.
* __v1.25.5 (2023-04-05)__: Updates to VEX2 writing routines (PROCEDURES, pointing_sector and datastream).
* __v1.25.6 (2023-04-12)__: Two bug fixes:
  * The OMS file writing Fortran function would write out of string boundaries for setups with more than 31 channels, into the setup file name. Only print the first 31 channels.
  * Update the Python wrap zone writing equivalent to the changes to the Fortran code introduced in 1.24.0.
* __v1.26.0 (2023-05-03)__: Skip writing pointing_sector lines in the $ANTENNA block of the VEX files for KVN stations.
* __v1.26.1 (2023-09-19)__: Bug fix: the 3rd and 6th cable wrap zones would use the lower instead of upper limit of the first axis.
* __v1.26.2 (2023-12-04)__: Bug fix in the Fortran code for wrap zones: a rare warning message had the wrong number of formatting parameters.
* __v1.26.3 (2024-05-16)__: Fixed typos in the sum file writing module.
* __v1.26.4 (2024-06-03)__: Fixed bug triggered by using GRABTO with NOSETUP.
* __v1.27.0 (2025-02-25)__: Merge with SCHED 11.8.
* __v1.28.0 (2025-08-20)__: Merge with SCHED 12.0.
* __v1.28.1 (2025-08-20)__: Fixed packaging bug: missing Vex2 Fortran include files.
* __v1.28.2 (2025-08-21)__: Fixed bug: a parameter to the Fortran function plbeam changed in size, but the call wasn't updated alongside.
* __v1.28.3 (2025-10-15)__: Fixed bug: VEXVRSN keyword was parsed as a number but handled as if it always was a string.


# Contact


**pySCHED** is maintained at the [Joint Institute for VLBI ERIC (JIVE)](https://www.jive.eu). You can reach the maintainers at [pysched@jive.eu](mailto:pysched@jive.eu).


# Acknowledgement


This project has received funding from the European Union’s Horizon 2020 research and innovation programme under grant agreement No 730884.