Git Product home page Git Product logo

vieschedpp's Introduction

VieSched++

VLBI scheduling software

Written by Matthias Schartner

Contact: [email protected]

Documentation: https://tuw-vievs.github.io/VieSchedpp/index.html

Reference

doi: https://doi.org/10.1088/1538-3873/ab1820

see: https://iopscience.iop.org/article/10.1088/1538-3873/ab1820

Getting started

Have a look at our YouTube channel https://www.youtube.com/channel/UCl2VPe7OrnznNtrh0_lwrqQ where we provide video tutorials. Additionally, the graphical user interface of VieSched++ contains a build in help. Read the text on the welcome page for more information.

License

VieSched++ Very Long Baseline Interferometry (VLBI) Scheduling Software

Copyright (C) 2018 Matthias Schartner

This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program. If not, see http://www.gnu.org/licenses/.

Installation

VieSched++ installers

Installers for Windows 10 and Ubuntu 18.04 are provided through the release page on GitHub!

Visit https://github.com/TUW-VieVS/VieSchedpp/releases.

Manual installation

This section descripes how to manually install VieSched++. Please note that we provide installers for several operating systems. It is a lot easier to use one of the installers instead of building VieSched++ manually!

The software consists of several parts:

  • VieSched++: the scheduler (this repository)
  • VieSched++ GUI (optional): the graphical user interface, hostet on https://github.com/TUW-VieVS/VieSchedppGUI
  • VieSched++ AUTO (optional): enables automated scheduling based on daily cronjob

It is highly recommended to use the GUI to create the VieSchedpp.xml input files!

The following code shows how to install all components of VieSched++ as well as their dependencies on a plain Ubuntu installation (tested with 18.04 and 20.04):

sudo apt update
sudo apt install git
sudo apt install build-essential
sudo apt install cmake 
sudo apt install libboost-all-dev

mkdir VieSchedpp
cd VieSchedpp

# make IAU_SOFA (get source code from any repository you like - see https://www.iausofa.org/)
git clone https://github.com/Starlink/sofa.git --single-branch --branch=vendor IAU_SOFA 
cd IAU_SOFA 
mkdir Release 
cd src/
make 
mv libsofa_c.a ../Release/
make clean
cd ../../

# make SGP4 (for satellite scheduling - see https://www.danrw.com/sgp4/)
git clone https://github.com/dnwrnr/sgp4.git
cd sgp4/
git checkout f5cb54b38
mkdir Release
cd Release
cmake -DCMAKE_BUILD_TYPE=Release ..
make
cd ../../

# make VieSched++
git clone https://github.com/TUW-VieVS/VieSchedpp.git 
cd VieSchedpp 
mkdir Release 
cd Release 
cmake -DCMAKE_BUILD_TYPE=Release .. 
make 
# [OPTIONAL] test installation: "$ ./VieSchedpp" 
cd ../../

# make VieSched++ GUI (optional - graphical user interface)
sudo apt install qt5-default libqt5charts5 libqt5charts5-dev libqt5network5 
git clone https://github.com/TUW-VieVS/VieSchedppGUI.git 
cd VieSchedppGUI
qmake VieSchedppGUI.pro 
make 
# [OPTIONAL] test installation: "$ ./VieSchedppGUI" 
make clean
cd ../

# install VieSched++ AUTO (optional - auto scheduling program)
# download VieSched++ AUTO
git clone --recurse-submodules https://github.com/TUW-VieVS/VieSchedpp_AUTO.git 
cd VieSchedpp_AUTO
# create virtual environment (I'm using venv here):
python3 -m venv venv
source venv/bin/activate
pip install -r requirements.txt
# [OPTIONAL] test installation: "$ python VieSchedpp_AUTO/VieSchedpp_AUTO.py -h"
# ===== alternative using miniconda: =====
# wget https://repo.anaconda.com/miniconda/Miniconda3-latest-Linux-x86_64.sh
# bash Miniconda3-latest-Linux-x86_64.sh # follow the installation instructions
# conda env create -f ./environment.yml # create new environment for VieSchedpp_AUTO
# conda activate VieSchedpp_AUTO # activate the new environment
# [OPTIONAL] test installation: "$ python VieSchedpp_AUTO/VieSchedpp_AUTO.py -h"

Tipps installing VieSchedpp

  • -DPATH_IAU_SOFA="./path/to/IAU_SOFA/" --> set path to IAU_SOFA library (default: "../IAU_SOFA/Release")
  • -DLINK_BOOST=False --> link against Boost libraries (default: "True")
  • If you have troubles finding boost try to set path -DBOOST_ROOT="./path/to/boost/"

Tipps installing VieSchedppGUI:

  • you can set path to IAU_SOFA library using qmake "IAU_SOFA=../../IAU_SOFA/libsofa_c.a" (default path is "../IAU_SOFA/Release")

Troubleshooting installation

If your Output contains some CMake warnings like:

CMake Warning at /usr/share/cmake-3.5/Modules/FindBoost.cmake:725 (message):
  Imported targets not available for Boost version 106400

check if your CMake version supports boost version and install the newest version of CMake from https://cmake.org/.


If you get error messages during linking with functions called: *boost* or iau_*:

Check if your c++ boost libraries and the SOFA library is found. If not set the path to this libraries in the CMakeLists.txt file.


If you have troubles getting boost to work simply try to build it without c++ boost libraries. (see Section "Tipps installing VieSchedpp")


If you still have troubles installing the software contact me: [email protected].

Software errors

VieSched++ is still in developing, there might be bugs or crashes.

Please always have a look at the log file and have a look if you get some [warning], [error] or [fatal] messages.

In case VieSched++ crashes or it reports an error in the log files please raise an issue at https://github.com/TUW-VieVS/VieSchedpp.

Follow the "Bug report" issue template and attach:

  • your current software version number (you can find it in the beginning of your log file, or in the .skd or .vex files - it is a hash code like f20be1498274232acb46cf44121f9e60278c6528)
  • your VieSchedpp.xml file
  • your catalog files
  • your log file VieSchedpp_yyyy-mm-dd_hh-mm-ss.sss.log
  • any other helpful information

Develop VieSched++

In case you want to develop VieSched++ have a look at the doxygen documentation and use an appropriate IDE.

vieschedpp's People

Contributors

h-wolf06 avatar matthias-schartner avatar white3 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar

vieschedpp's Issues

Error during installation on Ubuntu

Describe the bug
The manual installation failed when I ran the make command after the second "cmake -DCMAKE_BUILD_TYPE=Release .." (after "git clone https://github.com/TUW-VieVS/VieSchedpp.git"). I tried with both "-DCMAKE" and "-DCAMKE" in the step before (mentioned in issue #6). This seems to be a compilation error, independent of the libraries installed.

Version number
759e79c, most recent download

Screenshots / Output
Full output on terminal of entire installation process:
terminal.txt
Screenshot for the error message:
image

Desktop (please complete the following information):
I am working with Xubuntu 21.04 and gcc 10.3.0.

Additional context
Comment on terminal output in txt file: Line 299, "*** Now type 'make test' to install the library and run tests ***". I did this the first time when I went through the installation guide and everything was fine. This is my second attempt to install manually.

Segmentation fault when installing from zip-file download

Describe the bug
I tried download and installation via the provided zip-folder following the descriptions in the read-me file. However, when running the command to open the GUI I get the message "Segmentation Fault", when running ./VieSchedppGUI.sh

Version number
Latest provided file (08th Oct 2021)

To Reproduce
Steps to reproduce the behavior:

  1. downloaded the zip-folder for Ubuntu (https://github.com/TUW-VieVS/VieSchedpp/releases)
  2. unpacked zip-folder
  3. navigated to unpacked folder via terminal and ran ./VieSchedppGUI.sh

Screenshots / Output
screenshot-2021-10-11-01

Desktop (please complete the following information):
I am working with Xubuntu 21.04 and gcc 10.3.0.

Tree-based scan selection

Describe the solution you'd like
Implement a tree-based scan selection.
only follow a limited amount of branches.

observations to satellites

Is your feature request related to a problem? Please describe.
Add the possibility to schedule satellites

Describe the solution you'd like
Change std::vector<VieVS::Source> to new class SourceList, similar to Network.
Calculate satellite scheduling similar to implementation in VieVS.
Schedule Satellites as high impact scans.

Describe alternatives you've considered
Create new base class Source and two derived classes Quasar and Satellite.

Two different entries for $FREQ and $TRACKS in $MODE section in .vex file

Scheduling a session based on the sked catalog mode "256-16(R1-R4)" resulted in the following $MODE section in the .vex file, where we inadvertently got two different entries for both $FREQ and $TRACKS:

$MODE;
    def 256-16(R1-R4);
        ref $FREQ =             GEOSX                        ;
        ref $FREQ =             GEOSX_VDIF         : Oe : Ow ;
        ref $BBC =              RAEG_WIDE          : Oe : Ow ;
        ref $IF =               RAEG_WIDE          : Oe : Ow ;
        ref $TRACKS =           14U2L-1-1-B        : Oe : Ow ;
        ref $TRACKS =           VDIF/8032/2_format : Oe : Ow ;
        ref $PASS_ORDER =       passOrder          : Oe : Ow ;
        ref $ROLL =             NO_ROLL            : Oe : Ow ;
        ref $PHASE_CAL_DETECT = Standard           : Oe : Ow ;
    enddef;

Apparently, the GEOSX frequency set-up is not applied to any telescope, however, our field system refuses to work with the two mentionings of $FREQ. As we don't understand the origin, our current work-around is to check the .vex file after scheduling and to delete the line manually.

Interestingly, for $TRACKS we get two specifications which both get assigned to the same telescopes. As with the two lines for $FREQ, our field system refuses the two mentionings. The first line (with 14U2L) is unwanted, so we delete this, too, manually.

Having both options for $FREQ resp. $TRACKS in their "catalog" section further down in the .vex file does not seem to be a problem for the FS.

We have seen similar behaviour before when scheduling other sessions, also with two lines for $FREQ and $TRACKS each which our FS refuses. However, since those cases appeared when using self-defined frequency set-ups we rather assumed the error to be caused by the user.

improve observing mode

Is your feature request related to a problem? Please describe.
remove static observing mode and replace it with better implementation.

Describe the solution you'd like
Following the .vex format add classes for "Mode", "BBC", "IF", "TRACKS", "FREQS" ...
Link stations to different blocks.
Support of multiple observing modes.
Support of mixed observing modes.

Describe alternatives you've considered
station based observing mode?

Schedule campaign instead of single session

Describe the solution you'd like
Save results from schedules and create the next schedule based on previous schedules.
Create a new source list file with the number of target scans and number of scheduled scans.

python package conflict when following VieSchedpp_AUTO Install readme

Describe the bug
For VieSchedpp_AUTO, the step pip install -r requirements.txt produces this error on Ubuntu 21.04 with last main repo code. This is due to a version conflict in the requirements.txt

Version number
github hash: 1629df8

To Reproduce
Follow instructions and run pip install -r requirements.txt

Screenshots / Output

[...]
Collecting urllib3==1.26.5
  Downloading urllib3-1.26.5-py2.py3-none-any.whl (138 kB)
     |████████████████████████████████| 138 kB 188.5 MB/s 
INFO: pip is looking at multiple versions of pytz to determine which version is compatible with other requirements. This could take a while.
INFO: pip is looking at multiple versions of python-dateutil to determine which version is compatible with other requirements. This could take a while.
INFO: pip is looking at multiple versions of pyparsing to determine which version is compatible with other requirements. This could take a while.
INFO: pip is looking at multiple versions of ptyprocess to determine which version is compatible with other requirements. This could take a while.
INFO: pip is looking at multiple versions of pillow to determine which version is compatible with other requirements. This could take a while.
INFO: pip is looking at multiple versions of pexpect to determine which version is compatible with other requirements. This could take a while.
INFO: pip is looking at multiple versions of pandas to determine which version is compatible with other requirements. This could take a while.
INFO: pip is looking at multiple versions of numpy to determine which version is compatible with other requirements. This could take a while.
INFO: pip is looking at multiple versions of matplotlib to determine which version is compatible with other requirements. This could take a while.
INFO: pip is looking at multiple versions of lxml to determine which version is compatible with other requirements. This could take a while.
INFO: pip is looking at multiple versions of kiwisolver to determine which version is compatible with other requirements. This could take a while.
INFO: pip is looking at multiple versions of idna to determine which version is compatible with other requirements. This could take a while.
INFO: pip is looking at multiple versions of cycler to determine which version is compatible with other requirements. This could take a while.
INFO: pip is looking at multiple versions of <Python from Requires-Python> to determine which version is compatible with other requirements. This could take a while.
INFO: pip is looking at multiple versions of chardet to determine which version is compatible with other requirements. This could take a while.
INFO: pip is looking at multiple versions of certifi to determine which version is compatible with other requirements. This could take a while.
ERROR: Cannot install -r requirements.txt (line 16) and idna==3.1 because these package versions have conflicting dependencies.

The conflict is caused by:
    The user requested idna==3.1
    requests 2.25.1 depends on idna<3 and >=2.5

To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip attempt to solve the dependency conflict

ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/user_guide/#fixing-conflicting-dependencies

Desktop (please complete the following information):
Ubuntu 21.04, Python 3.9 venv.

Additional suggestions
After quick inspection, I decided to try to relax the version constraint on "requests" by editing the file requirements.txt to change requests==2.25.1 to just requests. I was then delivered requests version 2.26.0, which appears to work. So, unless you have better suggestions, I'd suggest relaxing the requests constraint, OR making it ==2.26.0. The current set of requirements is, surprisingly, internally incompatible.

Minor relative-path comment for Manual install Vieschedpp_AUTO instructions

Describe your issue here

On the Manual install page, this section exists:

# install VieSched++ AUTO (optional - auto scheduling program)
# download VieSched++ AUTO
git clone --recurse-submodules https://github.com/TUW-VieVS/VieSchedpp_AUTO.git 
cd VieSchedpp_AUTO
# create virtual environment (I'm using venv here):
python3 -m venv venv
source venv/bin/activate
pip install -r requirements.txt
# alternative using miniconda:
# wget https://repo.anaconda.com/miniconda/Miniconda3-latest-Linux-x86_64.sh
# bash Miniconda3-latest-Linux-x86_64.sh # follow the installation instructions
# conda env create -f ./VieSchedpp_AUTO/environment.yml # create new environment for VieSchedpp_AUTO
# conda activate VieSchedpp_AUTO # activate the new environment
# [OPTIONAL] test installation: "$ python VieSchedpp_AUTO/VieSchedpp_AUTO.py -h"

The venv way first has "cd VieSchedpp_AUTO" which means one is inside the AUTO-folder. These are very minor points, but:

  • The conda install appears to assume we're one level up from the AUTO-folder, so in a different folder than the venv way. Is this intentional, or should both be assumed to be at the same level?
  • The last point, [OPTIONAL] test installation: "$ python VieSchedpp_AUTO/VieSchedpp_AUTO.py -h" technically applies both the venv and conda ways, I presume. But this also assumes we're one level up from the AUTO-folder, so it won't run without at "cd .." up from the venv folder.

Really minor points, I know, but might as well note since I had a "huh?" moment when I copy pasted the test-line :).

Incompatible version of OpenSSL (Ubuntu 20.04)

Hello Matthias,

Describe the bug

qt.network.ssl: Incompatible version of OpenSSL

Version number
VieSched++ 1.2.1
Installed from VieSched++.Ubuntu.zip file

To Reproduce
Launch GUI with ./VieSchedppGUI.sh

Screenshots / Output
Got this output :

libpng warning: iCCP: known incorrect sRGB profile
qt.network.ssl: QSslSocket: cannot resolve CRYPTO_num_locks
qt.network.ssl: QSslSocket: cannot resolve CRYPTO_set_id_callback
qt.network.ssl: QSslSocket: cannot resolve CRYPTO_set_locking_callback
qt.network.ssl: QSslSocket: cannot resolve ERR_free_strings
qt.network.ssl: QSslSocket: cannot resolve EVP_CIPHER_CTX_cleanup
qt.network.ssl: QSslSocket: cannot resolve EVP_CIPHER_CTX_init
qt.network.ssl: QSslSocket: cannot resolve sk_new_null
qt.network.ssl: QSslSocket: cannot resolve sk_push
qt.network.ssl: QSslSocket: cannot resolve sk_free
qt.network.ssl: QSslSocket: cannot resolve sk_num
qt.network.ssl: QSslSocket: cannot resolve sk_pop_free
qt.network.ssl: QSslSocket: cannot resolve sk_value
qt.network.ssl: QSslSocket: cannot resolve SSL_library_init
qt.network.ssl: QSslSocket: cannot resolve SSL_load_error_strings
qt.network.ssl: QSslSocket: cannot resolve SSL_get_ex_new_index
qt.network.ssl: QSslSocket: cannot resolve SSLv3_client_method
qt.network.ssl: QSslSocket: cannot resolve SSLv23_client_method
qt.network.ssl: QSslSocket: cannot resolve SSLv3_server_method
qt.network.ssl: QSslSocket: cannot resolve SSLv23_server_method
qt.network.ssl: QSslSocket: cannot resolve X509_STORE_CTX_get_chain
qt.network.ssl: QSslSocket: cannot resolve OPENSSL_add_all_algorithms_noconf
qt.network.ssl: QSslSocket: cannot resolve OPENSSL_add_all_algorithms_conf
qt.network.ssl: QSslSocket: cannot resolve SSLeay
qt.network.ssl: Incompatible version of OpenSSL
qt.network.ssl: QSslSocket: cannot call unresolved function SSLv23_client_method
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_CTX_new
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_library_init
qt.network.ssl: QSslSocket: cannot call unresolved function ERR_get_error
qt.network.ssl: QSslSocket: cannot call unresolved function ERR_get_error
qt.network.ssl: QSslSocket: cannot call unresolved function SSLv23_client_method
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_CTX_new
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_library_init
qt.network.ssl: QSslSocket: cannot call unresolved function ERR_get_error
qt.network.ssl: QSslSocket: cannot call unresolved function ERR_get_error
qt.network.ssl: QSslSocket: cannot call unresolved function SSLv23_client_method
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_CTX_new
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_library_init
qt.network.ssl: QSslSocket: cannot call unresolved function ERR_get_error
qt.network.ssl: QSslSocket: cannot call unresolved function ERR_get_error
qt.network.ssl: QSslSocket: cannot call unresolved function SSLv23_client_method
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_CTX_new
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_library_init
qt.network.ssl: QSslSocket: cannot call unresolved function ERR_get_error
qt.network.ssl: QSslSocket: cannot call unresolved function ERR_get_error
qt.network.ssl: QSslSocket: cannot call unresolved function SSLv23_client_method
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_CTX_new
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_library_init
qt.network.ssl: QSslSocket: cannot call unresolved function ERR_get_error
qt.network.ssl: QSslSocket: cannot call unresolved function ERR_get_error
qt.network.ssl: QSslSocket: cannot call unresolved function SSLv23_client_method
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_CTX_new
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_library_init
qt.network.ssl: QSslSocket: cannot call unresolved function ERR_get_error
qt.network.ssl: QSslSocket: cannot call unresolved function ERR_get_error
qt.network.ssl: QSslSocket: cannot call unresolved function SSLv23_client_method
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_CTX_new
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_library_init
qt.network.ssl: QSslSocket: cannot call unresolved function ERR_get_error
qt.network.ssl: QSslSocket: cannot call unresolved function ERR_get_error
qt.network.ssl: QSslSocket: cannot call unresolved function SSLv23_client_method
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_CTX_new
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_library_init
qt.network.ssl: QSslSocket: cannot call unresolved function ERR_get_error
qt.network.ssl: QSslSocket: cannot call unresolved function ERR_get_error
qt.network.ssl: QSslSocket: cannot call unresolved function SSLv23_client_method
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_CTX_new
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_library_init
qt.network.ssl: QSslSocket: cannot call unresolved function ERR_get_error
qt.network.ssl: QSslSocket: cannot call unresolved function ERR_get_error
qt.network.ssl: QSslSocket: cannot call unresolved function SSLv23_client_method
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_CTX_new
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_library_init
qt.network.ssl: QSslSocket: cannot call unresolved function ERR_get_error
qt.network.ssl: QSslSocket: cannot call unresolved function ERR_get_error
qt.network.ssl: QSslSocket: cannot call unresolved function SSLv23_client_method
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_CTX_new
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_library_init
qt.network.ssl: QSslSocket: cannot call unresolved function ERR_get_error
qt.network.ssl: QSslSocket: cannot call unresolved function ERR_get_error
qt.network.ssl: QSslSocket: cannot call unresolved function SSLv23_client_method
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_CTX_new
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_library_init
qt.network.ssl: QSslSocket: cannot call unresolved function ERR_get_error
qt.network.ssl: QSslSocket: cannot call unresolved function ERR_get_error
qt.network.ssl: QSslSocket: cannot call unresolved function SSLv23_client_method
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_CTX_new
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_library_init
qt.network.ssl: QSslSocket: cannot call unresolved function ERR_get_error
qt.network.ssl: QSslSocket: cannot call unresolved function ERR_get_error
qt.network.ssl: QSslSocket: cannot call unresolved function SSLv23_client_method
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_CTX_new
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_library_init
qt.network.ssl: QSslSocket: cannot call unresolved function ERR_get_error
qt.network.ssl: QSslSocket: cannot call unresolved function ERR_get_error
qt.network.ssl: QSslSocket: cannot call unresolved function SSLv23_client_method
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_CTX_new
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_library_init
qt.network.ssl: QSslSocket: cannot call unresolved function ERR_get_error
qt.network.ssl: QSslSocket: cannot call unresolved function ERR_get_error
qt.network.ssl: QSslSocket: cannot call unresolved function SSLv23_client_method
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_CTX_new
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_library_init
qt.network.ssl: QSslSocket: cannot call unresolved function ERR_get_error
qt.network.ssl: QSslSocket: cannot call unresolved function ERR_get_error

and a windows opens in GUI with "Error while downloading files" as title. This windows contains the info :

error while downloading ftp://cddis.gsfc.nasa.gov/pub/vlbi/ivscontrol/master21.txt
error while downloading ftp://cddis.gsfc.nasa.gov/pub/vlbi/ivscontrol/master21-int.txt
error while downloading ftp://cddis.gsfc.nasa.gov/pub/vlbi/ivscontrol/master22.txt
error while downloading ftp://cddis.gsfc.nasa.gov/pub/vlbi/ivscontrol/master22-int.txt
error while downloading https://ivscc.gsfc.nasa.gov/IVS_AC/sked_cat/antenna.cat
error while downloading https://ivscc.gsfc.nasa.gov/IVS_AC/sked_cat/equip.cat
error while downloading https://ivscc.gsfc.nasa.gov/IVS_AC/sked_cat/flux.cat
error while downloading https://ivscc.gsfc.nasa.gov/IVS_AC/sked_cat/freq.cat
error while downloading https://ivscc.gsfc.nasa.gov/IVS_AC/sked_cat/hdpos.cat
error while downloading https://ivscc.gsfc.nasa.gov/IVS_AC/sked_cat/loif.cat
error while downloading https://ivscc.gsfc.nasa.gov/IVS_AC/sked_cat/mask.cat
error while downloading https://ivscc.gsfc.nasa.gov/IVS_AC/sked_cat/modes.cat
error while downloading https://ivscc.gsfc.nasa.gov/IVS_AC/sked_cat/position.cat
error while downloading https://ivscc.gsfc.nasa.gov/IVS_AC/sked_cat/rec.cat
error while downloading https://ivscc.gsfc.nasa.gov/IVS_AC/sked_cat/rx.cat
error while downloading https://ivscc.gsfc.nasa.gov/IVS_AC/sked_cat/source.cat.geodetic.good
error while downloading https://ivscc.gsfc.nasa.gov/IVS_AC/sked_cat/tracks.cat
error while downloading https://datacenter.iers.org/data/latestVersion/9_FINALS.ALL_IAU2000_V2013_019.txt

Desktop :

  • OS: Linux Ubuntu 20.04.3
  • OpenSSL 1.1.1f 31 Mar 2020 (installed via package manager)

Thanks for your help!
Arnaud

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.