Updated readme

.gitattributes

@@ -1 +0,0 @@
-images/*.png filter=lfs diff=lfs merge=lfs -text

.github/workflows/sync-to-hf-space.yml

@@ -2,101 +2,44 @@
 name: Sync to Hugging Face Space
 
 on:
-  push: all history
-          lfs: false    # Checkout LFS pointers first, then explicitly fetch
-
-      - name: Setup Git LFS
-        run: |
-          git lfs install --system --skip-repo # Install LFS
+  push:
     branches:
-      - main
+      - main # Or whatever your default branch is
 
 jobs:
   sync:
     runs-on: ubuntu-latest
     steps:
       - name: Checkout repository
-        uses: actions/checkout@v4
+        uses: actions/checkout@v3
         with:
-          fetch-depth: 0 # Fetch all history initially, we might not push it all to HF
-          lfs: true     # Ensure LFS files are checked out
-
-      - name: Install Git LFS
-        run: | globally
-          echo "Git LFS installed"
-
-      - name: Fetch LFS files from origin (GitHub)
-        # This step ensures the runner downloads the actual LFS file content
-        # associated with the pointers checked out in the previous step.
-        run: |
-          git lfs fetch --all origin 
-          git lfs checkout # This replaces pointers with actual files
-          echo "LFS files fetched and checked out"
-          git lfs ls-files # List LFS files to confirm they are present
-
-      - name: Push to Hugging Face Space
-        env:
-          
-          git lfs install --skip-repo # Initialize LFS for the git commands
+          fetch-depth: 0 # Fetch all history for accurate diffs
 
       - name: Push to Hugging Face Space
         env:
           HF_TOKEN: ${{ secrets.HF_TOKEN }}
-          SPACE_ID: GuitarGoogle/Prophet-commodity-stock-analysis # Corrected username based on previous context
-        run:HF_TOKEN: ${{ secrets.HF_TOKEN }}
+          # Your Hugging Face username
+          HF_USERNAME: GuitarGeorge
+          # The ID of your Space (username/space-name)
           SPACE_ID: GuitarGeorge/Prophet-commodity-stock-analysis
         run: |
           echo "Attempting to push to Hugging Face Space: $SPACE_ID"
+          # Add Hugging Face as a remote
+          # The username in the URL is important for Git to use the correct token
+          git remote add hf_space "https://dummy:${HF_TOKEN}@huggingface.co/spaces/${SPACE_ID}"
           
-          git config --global user.email "[email protected]"
-          git config --global user |
-          echo "Attempting to push to Hugging Face Space: $SPACE_ID"
+          # Check if the remote was added
+          git remote -v
           
+          # Configure Git user (sometimes needed in CI, though token auth often bypasses this need for commit identity)
           git config --global user.email "[email protected]"
           git config --global user.name "GitHub Action"
-
-          # Set up the Hugging Face remote
-          # Using dummy username as the token should handle.name "GitHub Action"
-
-          # Add Hugging Face remote. Using a distinct name for the user part can help.
-          # The token is the password.
-          git remote add hf_space "https://hf_ auth
-          git remote add hf_space "https://dummy:${HF_TOKEN}@huggingface.co/spaces/${SPACE_ID}"
-          git remote -v
-
-          # Ensure local LFS files are present (fetched from originaction_user:${HF_TOKEN}@huggingface.co/spaces/${SPACE_ID}"
-          git remote -v
-
-          # Explicitly tell Git to use Hugging Face's LFS transfer agent for this remote.
-          # during checkout with lfs:true)
-          # If checkout with lfs:true is insufficient, explicitly fetch:
-           This is often a key step.
-          git config lfs.https://huggingface.co/spaces/${# echo "Fetching LFS objects from origin (GitHub)..."
-          # git lfs fetch --all origin 
-
-          SPACE_ID}.git/info/lfs.locksverify true
-          git config lfs.https://huggingface# Explicitly push LFS objects to the Hugging Face remote first
-          echo "Pushing LFS objects to h.co/spaces/${SPACE_ID}.git/info/lfs.access hf_transfer
-
-          # Push Lf_space (Hugging Face)..."
-          git lfs push --all hf_space
-
-          #FS objects specifically to the Hugging Face remote.
-          # This ensures the LFS files are uploaded to HF's LFS storage.
-          echo "Pushing LFS objects to hf_space..."
-          git lfs push --all hf_space
-          # As a diagnostic, check if LFS thinks they are uploaded for this remote:
-          # git Strategy: Try to push the current commit (HEAD) as a fresh 'main' branch to Hugging Face
-          # This attempts to overwrite the 'main' branch on HF with only the current commit's state and its direct LFS pointers.
-          # It might sever the history on the HF remote from its previous state if the histories are incompatible,
-          # which could be what's needed if old commits are causing the pre-receive hook to fail.
-          echo "Push lfs ls-files | awk '{print $1}' | xargs git lfs check Pushed to hf_space 
-
-          # Push the Git references (commits, LFS pointers).
-          echo "Pushing Git references to hf_space..."
-          git push --force hf_space HEAD:refs/heads/main
           
-          echo "ing Git references (current HEAD as main) to hf_space..."
-          git push --force hf_space HEAD:refs/heads/main 
+          # Attempt to push. Using -f to force push might be needed if the histories diverge,
+          # but be cautious. A safer approach is to ensure clean history.
+          # For a simple sync, `git push hf_space main` might be enough if main on HF mirrors main on GitHub.
+          # If you want to ensure the Space always reflects the GitHub main branch, a force push is common.
+          # Be aware that force push overwrites the history on the remote.
+          git push --force hf_space HEAD:refs/heads/main
           
           echo "Push to Hugging Face Space completed."

README.md

@@ -83,30 +83,30 @@ The following table summarizes the performance metrics observed for each ticker
 *(These plots illustrate how the model's forecast (blue line) and confidence interval (shaded area) compared against the actual test data (black dots) during a historical backtest run.)*
 
 **DBA - Test Forecast vs. Actuals**
-![DBA Test Forecast](images/DBA_test_forecast_vs_actual.png)
+![DBA Test Forecast](https://drive.google.com/uc?export=view&id=112aylZnv3NKTUQWz5HrU2hsRwaNSymMg)
 
 **FCX - Test Forecast vs. Actuals**
-![FCX Test Forecast](images/FCX_test_forecast_vs_actual.png)
+![FCX Test Forecast](https://drive.google.com/uc?export=view&id=10n3XTm9Rsg02_kEL6BcMn3gCUHX_Ws9s)
+)
 
 **GLD - Test Forecast vs. Actuals**
-![GLD Test Forecast](images/GLD_test_forecast_vs_actual.png)
+![GLD Test Forecast](https://drive.google.com/uc?export=view&id=10u1NiRooMPFsKzuSazP6JmIq6os94nyx)
+)
 
 **NEM - Test Forecast vs. Actuals**
-![NEM Test Forecast](images/NEM_test_forecast_vs_actual.png)
+![NEM Test Forecast](https://drive.google.com/uc?export=view&id=10w2mCXzsBy6mciHzVLuG_Zhm00cFEGgu)
 
 **SLV - Test Forecast vs. Actuals**
-![SLV Test Forecast](images/SLV_test_forecast_vs_actual.png)
+![SLV Test Forecast](https://drive.google.com/uc?export=view&id=10rWqezVNT6-6XVNyfe6YYrsOwiQ3pmH)
 
 **UNG - Test Forecast vs. Actuals**
-![UNG Test Forecast](images/UNG_test_forecast_vs_actual.png)
+![UNG Test Forecast](https://drive.google.com/uc?export=view&id=10mM2ldm3ITnEGf9hHlLHfnWfhkjjxlOB)
 
 **USO - Test Forecast vs. Actuals**
-![USO Test Forecast](images/USO_test_forecast_vs_actual.png)
-
-![XOM Test Forecast](https://drive.google.com/uc?export=view&id=112aylZnv3NKTUQWz5HrU2hsRwaNSymMg)
+![USO Test Forecast](https://drive.google.com/uc?export=view&id=10mmxq7bX-stgWfp6PzABEVCuLW83K8Vc)
 
 **XOM - Test Forecast vs. Actuals**
-![XOM Test Forecast](images/XOM_test_forecast_vs_actual.png)
+![XOM Test Forecast](https://drive.google.com/uc?export=view&id=110TK2aASouWvpRfiifVo8M5w5OEN7xv_)
 
 *(Image for XOM provided shows a wide confidence interval, indicating high uncertainty in the long-term forecast for this particular backtest period).*