Set up test Replan Central

 Set up new conda

# Get a clean shell with no conda environment
env -i bash --rcfile /etc/profile

# Define the location for the test environment
export ska_dir=/fido.real/kadi/arc3_test

wget https://github.com/conda-forge/miniforge/releases/download/24.9.2-0/Miniforge3-24.9.2-0-Linux-x86_64.sh
wget https://github.com/conda-forge/miniforge/releases/download/24.9.2-0/Miniforge3-24.9.2-0-Linux-x86_64.sh.sha256
shasum -c Miniforge3-24.9.2-0-Linux-x86_64.sh.sha256

bash Miniforge3-24.9.2-0-Linux-x86_64.sh -b -p $ska_dir

export PATH=${ska_dir}/bin:$PATH

# Install ska3 environment in test area.
# Note that since arc is not a ska3-flight package just now, one could use ska3-flight instead of ska3-flight-latest,
# but it might be better test practice to use latest.
#conda install --override-channels -c https://icxc.cfa.harvard.edu/aspect/ska3-conda/flight \
#  ska3-flight-latest ska3-core-latest ska3-perl-latest


# if testing to install in flight - use ska3-flight not ska3-flight-latest
mamba install --override-channels -c https://icxc.cfa.harvard.edu/aspect/ska3-conda/flight ska3-flight ska3-core ska3-perl python==3.11.8  -c conda-forge


cd $ska_dir
mkdir -p data/arc3
mkdir -p www/ASPECT/arc3
# Copy the data over from the flight replan central to seed the testing
for file in ACE.h5 GOES_X.h5 hrc_shield.h5 ACE_hourly_avg.npy;
do rsync -a /proj/sot/ska/data/arc3/$file data/arc3/;
done;

# Link kadi data
ln -s /proj/sot/ska/data/kadi data/kadi
# Link eng archive data
ln -s /proj/sot/ska/data/eng_archive data/eng_archive
# Link dsn summary
ln -s /proj/sot/ska/data/dsn_summary data/dsn_summary


# Source into the new SKA
source ${ska_dir}/bin/ska_envs.sh

# Install arc
cd ~/git/arc
# Checkout a version for testing such as timeline-avail-comms or master
git checkout timeline-avail-comms
# review paths with make -n
make -n install
# Install to $SKA which should be ${ska_dir} in this example
make install

mkdir -p $SKA_DATA/arc3/iFOT_time_machine

# The running user will also need a .netrc file with credentials for occweb

# From that point, the scripts referenced in task_schedule.cfg should be runnable
# from $SKA/share/arc3 and the output for www should be visible in $SKA/www/ASPECT/arc3.
# If testing will require "live" testing to a webserver, that can be accomplished with
# symbolic links.