batch compute resources update

sds_data_manager/constructs/compute_resources.py

@@ -168,7 +168,10 @@ def __init__(
             type="CONTAINER",
             platform_capabilities=["FARGATE"],
             container_properties={
-                "image": f"{repo.repository_uri}:{account_name}",
+                "image": f"{repo.repository_uri}:latest",
+                "environment": [
+                    {"name": "SPICE_DIRECTORY", "value": "/mnt/spice"},
+                ],
                 "mountPoints": [
                     {
                         "sourceVolume": efs_instance.volume_name,

sds_data_manager/lambda_code/efs_lambda/lambda_function.py

@@ -55,12 +55,21 @@ def write_data_to_efs(s3_key: str, s3_bucket: str):
 
     logging.debug("After downloading file: %s", os.listdir(mount_path))
 
-    # Attitude naming convention is this:
+    # TODO: we only want historical attitude kernels delivery
+    #  following each track (3/wk)
+    # Make certain it does not start with imap_pred_ (only imap_)
+    # https://confluence.lasp.colorado.edu/display/IMAP/IMAP+POC+External+Reference+Documents
+    # pg 17 of 7516-9163 MOC Data Products Guide
+    # Historical attitude naming convention is this:
     # imap_yyyy_doy_yyyy_doy_##.ah.bc and
     # imap_yyyy_doy_yyyy_doy_##.ah.a
     if filename.endswith(".ah.a") or filename.endswith(".ah.bc"):
         create_symlink(download_path, attitude_symlink_path)
 
+    # TODO: reconstructed would be ideal (change to imap_recon)
+    # We need to confirm that reconstructed can be delivered 3/wk
+    # Right now document says 1/wk
+    # But nom is least ideal (after burn and pred)
     # Ephemeris naming convention is this:
     # Eg. imap_nom_yyyymmdd_yyyymmdd_v##.bsp
     # The reason we check startswith is because other ephemeris