Numerator Evaluation with counterterms

.github/workflows/gamma_loop_tests.yml

@@ -18,10 +18,10 @@ jobs:
 
     steps:
     - uses: actions/checkout@v3
-    - name: Set up Python 3.11
+    - name: Set up Python 3.12
       uses: actions/setup-python@v3
       with:
-        python-version: "3.11"
+        python-version: "3.12"
 #    - name: Install TeXlive
 #      run: sudo apt-get update && sudo apt-get install texlive-full texlive-publishers texlive-science latexmk cm-super feynmf
     - name: Install dependencies

.gitignore

@@ -44,12 +44,18 @@ logos/
 *.swp
 
 # ignore vscode repo
-.vscode/
+.vscode
 
 # compiled library
 *.a
 *.dylib
 
+# ignore gammaLoop cards
+*.gL
+
+# ignore dot files as they are usually for testing only
+*.dot
+
 # PyInstaller
 #  Usually these files are written by a python script from a template
 #  before PyInstaller builds the exe, so as to inject date/other infos into it.
@@ -69,6 +75,10 @@ ignore/
 
 src/test_resources/gammaloop_models/*.dat
 
+src/test_resources/trees
+
+GL_OUTPUT*
+
 src/test_resources/TEST_AMPLITUDE_*
 # Sadly this does not work because the exclusion above is for an entire directory
 !src/test_resources/TEST_AMPLITUDE_*/GL_OUTPUT/output_metadata.yaml
@@ -193,8 +203,17 @@ default.nix
 # Ignore the local test resources
 src/test_resources/qqddg/
 
+
+# Ignore the local compiled numerators 
+/*.cpp
+/*.so
+
+
+# Ignore tmp compiled files:
+
+TMP_COMPILED/
 # My own process outputs
 process_outputs
-
+ignore/
 # the default log file
-log.glog/
+log.glog/

.vscode/settings.json

@@ -0,0 +1,15 @@
+{
+  "editor.formatOnSave": true,
+  "rust-analyzer.check.command": "clippy",
+  "rust-analyzer.runnables.extraArgs": ["--no-default-features"],
+  "rust-analyzer.runnables.extraTestBinaryArgs": [
+    "--nocapture"
+  ],
+  "conventionalCommits.scopes": ["cargo", "python", "build", "rust"],
+  "rust-analyzer.linkedProjects": ["./Cargo.toml"],
+  "github.copilot.enable": {
+    "*": true
+  },
+  "svg.preview.background": "white",
+  "workbench.activityBar.location": "top",
+}

.zed/settings.json

@@ -3,5 +3,41 @@
 // For a full list of overridable settings, and general information on folder-specific settings,
 // see the documentation: https://zed.dev/docs/configuring-zed#folder-specific-settings
 {
-
+  "shell": {
+    "program": "bash"
+  },
+  "ui_font_family": "Iosevka-Custom-Heavy",
+  "buffer_font_family": "Iosevka-Custom-Heavy",
+  "lsp": {
+    "rust-analyzer": {
+      "initialization_options": {
+        "inlayHints": {
+          "typeHints": true,
+          "maxLength": null,
+          "lifetimeElisionHints": {
+            "useParameterNames": true,
+            "enable": "skip_trivial"
+          },
+          "closureReturnTypeHints": {
+            "enable": "always"
+          }
+        },
+        "cargo": {
+          "features": "all"
+        },
+        "diagnostics": {
+          "experimental": {
+            "enable": true
+          }
+        },
+        // To disable the checking entirely
+        // (ignores all cargo and check settings below)
+        "checkOnSave": true,
+        "check": {
+          "onSave": true,
+          "features": ["all"]
+        }
+      }
+    }
+  }
 }

.zed/tasks.json

@@ -0,0 +1,40 @@
+// Static tasks configuration.
+//
+// Example:
+
+[
+  {
+    "label": "Example task",
+    "command": "for i in {1..5}; do echo \"Hello $i/5\"; sleep 1; done",
+    //"args": [],
+    // Env overrides for the command, will be appended to the terminal's environment from the settings.
+    "env": { "foo": "bar" },
+    // Current working directory to spawn the command into, defaults to current project root.
+    //"cwd": "/path/to/working/directory",
+    // Whether to use a new terminal tab or reuse the existing one to spawn the process, defaults to `false`.
+    "use_new_terminal": false,
+    // Whether to allow multiple instances of the same task to be run, or rather wait for the existing ones to finish, defaults to `false`.
+    "allow_concurrent_runs": false,
+    // What to do with the terminal pane and tab, after the command was started:
+    // * `always` — always show the terminal pane, add and focus the corresponding task's tab in it (default)
+    // * `never` — avoid changing current terminal pane focus, but still add/reuse the task's tab there
+    "reveal": "always",
+    // What to do with the terminal pane and tab, after the command had finished:
+    // * `never` — Do nothing when the command finishes (default)
+    // * `always` — always hide the terminal tab, hide the pane also if it was the last tab in it
+    // * `on_success` — hide the terminal tab on task success only, otherwise behaves similar to `always`
+    "hide": "never",
+    // Which shell to use when running a task inside the terminal.
+    // May take 3 values:
+    // 1. (default) Use the system's default terminal configuration in /etc/passwd
+    //      "shell": "system"
+    // 2. A program:
+    //      "shell": {
+    //        "program": "sh"
+    //      }
+    // 3. A program with arguments:
+    "shell": {
+      "program": "bash"
+    }
+  }
+]

ARCHITECTURE.md

@@ -0,0 +1,7 @@
+# Planned features and interactions
+
+All configuration settings (not process specific) should be settable from a file (a default is provided). It should be overridable at run time. Overriding does not modify the file.
+
+The model file uses the ufo format. When loading, this gets converted to a yaml file. All _independent_ values (external parameters as per UFO) in this file should be overridable, and all _dependent_ values are computed and modified when the values are updated. This modifies the yaml file. When using any parameter, or derived value we avoid recomputing it and just use its value.
+
+Ideally the run card processing should batch operations, such that setting different values are first parsed and then applied in one go. This is to avoid recomputing dependent values multiple times. Currently this is done by serializing the settings and then loading them in rust only after.