Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
projects:quantum:distributed [2024/12/05 14:48] – kymkiprojects:quantum:distributed [2024/12/06 16:05] (current) – kymki
Line 1: Line 1:
-{{ :wiki:distributed_quantum_computing:qcqc.png?1300x400 |}}+<html> 
 +<head> 
 +  <meta charset="UTF-8"> 
 +  <meta name="viewport" content="width=device-width, initial-scale=1.0"> 
 +  <title>Ramble Meter</title> 
 +  <style> 
 +    /* Container for the entire Ramble Meter */ 
 +    .ramble-meter-container { 
 +      display: flex; 
 +      align-items: center; 
 +      justify-content: center; 
 +      margin: 20px 0; 
 +    }
  
-Massive investments are being made in the European landscape of quantum computing. The question is what frameworks that enable orchestration of calculations to only deploy the most optimal problem formulation on the most suitable piece of hardware.+    /* Ramble Meter */ 
 +    .ramble-meter { 
 +      position: relative; 
 +      width: 200px; /* Scaled down */ 
 +      height: 40px; /* Scaled down */ 
 +      background: linear-gradient(to right, green, yellow, orange, red); 
 +      border-radius: 20px; 
 +      overflow: hidden; 
 +      box-shadow: 0 2px 8px rgba(0, 0, 0, 0.3); 
 +    }
  
-==== Problem statement ====+    /* Needle */ 
 +    .needle { 
 +      position: absolute; 
 +      top: 5px; /* Adjust for centering */ 
 +      left: 50%; /* Default position */ 
 +      width: 4px; /* Visible width */ 
 +      height: 30px; 
 +      background: black; 
 +      border-radius: 2px; 
 +      z-index: 2; 
 +      box-shadow: 0 0 10px rgba(0, 0, 0, 0.5); /* Glow effect */ 
 +    }
  
-As a researcher and innovator in the quantum life-science area, I want to be able to develop or test an algorithm locally on my laptop and iteratively expand on it in terms of parameters, noise models used, systems analysed etc. I want to define a grid of parameters, something like: +    /* Label in the middle of the meter */ 
-<html> +    .meter-label { 
-<head> +      position: absolute; 
-  <link href="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/11.7.0/styles/monokai-sublime.min.css" rel="stylesheet"> +      top: 50%; 
-  <script src="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/11.7.0/highlight.min.js"></script> +      left: 50%; 
-  <script>hljs.highlightAll();</script> +      transform: translate(-50%, -50%); 
-</head> +      font-family: Arial, sans-serif; 
-<body>+      font-size: 12px; /* Adjusted for smaller size */ 
 +      font-weight: bold; 
 +      color: #fff; 
 +      text-shadow: 0 2px 4px rgba(0, 0, 0, 0.5); 
 +      z-index: 3; 
 +    }
  
-print(hello)+    /* Tooltip styling */ 
 +    .tooltip { 
 +      visibility: hidden; 
 +      width: 250px; 
 +      background-color: #222; 
 +      color: #fff; 
 +      text-align: center; 
 +      padding: 10px; 
 +      border-radius: 5px; 
 +      position: absolute; 
 +      top: 50%; /* Vertically aligned */ 
 +      left: 110%; /* Position to the right of the meter */ 
 +      transform: translateY(-50%); 
 +      font-size: 12px; 
 +      z-index: 10; 
 +      box-shadow: 0 2px 5px rgba(0, 0, 0, 0.3); 
 +    }
  
 +    /* Show tooltip on hover */
 +    .ramble-meter:hover + .tooltip {
 +      visibility: visible;
 +    }
 +
 +    /* Wrapper for positioning the tooltip and meter */
 +    .ramble-wrapper {
 +      position: relative;
 +      display: flex;
 +      align-items: center;
 +    }
 +  </style>
 +  <script>
 +    document.addEventListener("DOMContentLoaded", () => {
 +      const needle = document.querySelector(".needle");
 +      const rambleMeter = document.querySelector(".ramble-meter");
 +      const level = rambleMeter.getAttribute("data-level"); // Read the level from the attribute (0-100)
 +      needle.style.left = `${Math.min(Math.max(level, 0), 100)}%`; // Clamp between 0 and 100
 +    });
 +  </script>
 +</head>
 +<body>
 +  <!-- Ramble Meter -->
 +  <div class="ramble-meter-container">
 +    <div class="ramble-wrapper">
 +      <div class="ramble-meter" data-level="10"> <!-- Adjust level here (0-100) -->
 +        <div class="meter-label">Ramble Meter</div>
 +        <div class="needle"></div>
 +      </div>
 +      <div class="tooltip">This post is very close to being completely finished. Not that rambly at all.</div>
 +    </div>
 +  </div>
 </body> </body>
 </html> </html>
  
 +{{ :wiki:distributed_quantum_computing:qcqc.png?1300x400 |}}
  
 +Massive investments are being made in the European landscape of quantum computing. The question is what frameworks that enable orchestration of calculations to only deploy the most optimal problem formulation on the most suitable piece of hardware.
  
 +==== Problem statement ====
 +
 +As a researcher and innovator in the quantum life-science area, I want to be able to develop or test an algorithm locally on my laptop and iteratively expand on it in terms of parameters, noise models used, systems analysed etc. I want to define a grid of parameters, something like:
  
 hyperparam_grid = [ hyperparam_grid = [
Line 62: Line 152:
     Create and append noise_spec (function: apply_noise_model, dependencies: noise_dependencies, noise_model: noise_model, ansatz_type: ansatz_type)     Create and append noise_spec (function: apply_noise_model, dependencies: noise_dependencies, noise_model: noise_model, ansatz_type: ansatz_type)
  
-Workflow of dependencies for each wavefunction ansatz:+Which yields a workflow of dependencies for each wavefunction ansatz: 
     "assemble_hamiltonian" -> "prepare_ansatz" -> "run_vqe_simulation" -> "apply_noise_model"     "assemble_hamiltonian" -> "prepare_ansatz" -> "run_vqe_simulation" -> "apply_noise_model"
  
Line 268: Line 359:
 </head> </head>
 <body> <body>
 +<pre><code class="python">
 def build_workflow(): def build_workflow():
     step_name = "build_workflow"     step_name = "build_workflow"
Line 363: Line 454:
         print(f"Workflow {workflow_graph.processgraphid} submitted")         print(f"Workflow {workflow_graph.processgraphid} submitted")
  
 +</code></pre>
 </body> </body>
 </html> </html>
Line 377: Line 468:
 </head> </head>
 <body> <body>
 +<pre><code class="python">
 def generate_one_electron_integrals_spec(nodename): def generate_one_electron_integrals_spec(nodename):
     one_electron_uuid = str(uuid.uuid4())     one_electron_uuid = str(uuid.uuid4())
Line 389: Line 480:
         )         )
     )     )
 +</pre></code>
  
 </body> </body>
Line 403: Line 494:
 </head> </head>
 <body> <body>
 +<pre><code class="python">
 from quantum_workflow.hamiltonian import ( from quantum_workflow.hamiltonian import (
     calculate_one_electron_integrals,     calculate_one_electron_integrals,
Line 491: Line 582:
          
     etc..      etc.. 
 +</code></pre>
 </body> </body>
 </html> </html>
Line 505: Line 596:
 </head> </head>
 <body> <body>
 +<pre><code class="python">
 from pyscf import gto, scf, ao2mo from pyscf import gto, scf, ao2mo
  
Line 550: Line 641:
         raise e         raise e
     return uuid     return uuid
 +    </code></pre>
 </body> </body>
 </html> </html>