(quantum computing) Examples of code for a "Bell state" : IBM quantum composer vs. OpenQASM vs. Qiskit

 

• https://quantum-computing.ibm.com/composer/files/new "Quantum Composer" IDE to build Q-progs : "Composer has a customizable set of tools that allow you to build, visualize, and run quantum circuits on quantum hardware or simulators".
• graphical editor for openQASM  or Qiskit formalisms

Examples of code generated in the step by step tutorial to create a "Bell state"

https://quantum-computing.ibm.com/composer/docs/iqx/example-circuits/bell

Same code, but different languages; done on the Quantum Composer ide following the initial step by step guide.

The Bell test demonstrates that measurements of an entangled state cannot be explained by any local hidden variable theory, and that there must be correlations that are beyond classical.

from: https://quantum-computing.ibm.com/composer/docs/iqx/example-circuits/bell

* Quantum Composer

* OpenQASM

OPENQASM 2.0;

include "qelib1.inc";

qreg q[2];

creg c[2];

h q[0];

cx q[0],q[1];

measure q[0] -> c[0];

measure q[1] -> c[1];

* Qiskit

from qiskit import QuantumRegister, ClassicalRegister, QuantumCircuit

from numpy import pi

qreg_q = QuantumRegister(2, 'q')

creg_c = ClassicalRegister(2, 'c')

circuit = QuantumCircuit(qreg_q, creg_c)

circuit.h(qreg_q[0])

circuit.cx(qreg_q[0], qreg_q[1])

circuit.measure(qreg_q[0], creg_c[0])

circuit.measure(qreg_q[1], creg_c[1])

Quantum computing resources

Quantum platforms, libraries, and learning platforms

Qiskit : open source lib

"Qiskit Machine Learning introduces fundamental computational building blocks - such as Quantum Kernels and Quantum Neural Networks - used in different applications, including classification and regression. On the one hand, this design is very easy to use and allows users to rapidly prototype a first model without deep quantum computing knowledge. On the other hand, Qiskit Machine Learning is very flexible, and users can easily extend it to support cutting-edge quantum machine learning research."

• https://qiskit.org/documentation/qc_intro.html quantum computing (QC) in a nutshell
• https://qiskit.org/documentation/machine-learning/ ML on QC 
• https://learn.qiskit.org/course/machine-learning/introduction 
• https://github.com/Qiskit/qiskit-machine-learning Github repo for Qiskit

DELF University quantum program

Long time research center on quantum computing. (sources < TPE 2001)

• https://qutech.nl 
• https://qutech.nl/research-engineering/quantum-computing/  (qu-algo & qu-prog)
• https://qutech.nl/research-engineering/quantum-internet/ (qu-network)
• https://qutech.nl/research-engineering/qubit-research/ (qu-infra)
• https://qutechacademy.nl/online-learning/online-courses/  Massive Online Open Courses (MOOC).

Community

community focused on quantum machine learning

• https://www.pennylane.ai/qml/   QML Quantum machine learning

IBM

• https://quantum-computing.ibm.com/ "IBM offers cloud access to the most advanced quantum computers available. Learn, develop, and run programs with our quantum applications and systems.
• https://quantum-computing.ibm.com/docs/
• https://quantum-computing.ibm.com/composer/files/new "Quantum Composer" IDE to build Q-progs : "Composer has a customizable set of tools that allow you to build, visualize, and run quantum circuits on quantum hardware or simulators".
• graphical editor for openQASM or Qiskit formalisms

source : 

• meetup  Technical Group by IBM, 
• 03 Nov 2022 https://www.meetup.com/technical-group-hosted-by-ibm/events/287144510/ 
• Sean Wagner, IBM Quantum Technical Ambassador

docker : list containers in a specific network

 

List containers in a precise 

$ docker network ls
NETWORK ID     NAME                               DRIVER    SCOPE
f732a9b3c5a1   bridge                             bridge    local
7ec614323767   host                               host      local
...

docker network inspect     -f '{{ range $key, $value := .Containers }}{{printf "%s: %s\n" $key .Name}}{{ end }}' <NETWORK NAME>
<ID> <Name>

common regexp

 https://owasp.org/www-community/OWASP_Validation_Regex_Repository

common regexp use-cases

Generating a cookie secret

Generating a cookie secret 

required step for a lot of web-based use-case when a cookie must be stored on the client side, for example with oauth2-proxy to set-up remote authentication.

• docker / python 

docker run -ti --rm python:3-alpine python -c 'import secrets,base64; print(base64.b64encode(base64.b64encode(secrets.token_bytes(16))));'

Followings solutions are from : https://oauth2-proxy.github.io/oauth2-proxy/docs/configuration/overview (v7.2.x)

• Python

python -c 'import os,base64; print(base64.urlsafe_b64encode(os.urandom(32)).decode())'

• Bash

dd if=/dev/urandom bs=32 count=1 2>/dev/null | base64 | tr -d -- '\n' | tr -- '+/' '-_'; echo

• Open SSL

openssl rand -base64 32 | tr -- '+/' '-_'

• PowerShell

# Add System.Web assembly to session, just in case
Add-Type -AssemblyName System.Web
[Convert]::ToBase64String([System.Text.Encoding]::UTF8.GetBytes([System.Web.Security.Membership]::GeneratePassword(32,4))).Replace("+","-").Replace("/","_")

• Terraform

# Valid 32 Byte Base64 URL encoding set that will decode to 24 []byte AES-192 secret
resource "random_password" "cookie_secret" {
  length           = 32
  override_special = "-_"
}

Caddy + xcaddy within a docker container

Start Caddy within a docker container and add a plugin.

https://caddyserver.com/docs/modules/security

./docker-compose.yml

version: '3.4'
networks:
  monitor-net:
    driver: bridge
volumes:
    caddy_data: {}
services:
  caddy:
    # cf. https://github.com/caddyserver/caddy/releases
    # image: caddy:2.5.0
    build:
      context: ./caddy/ # where to look for the Dockerfile
      dockerfile: Dockerfile # actual name of the Dockerfile
      args:
        image_ref: caddy:2.5.0
    container_name: caddy
    ports:
      - "80:80"
      - "443:443"
    volumes:
      - ./caddy:/etc/caddy
      - caddy_data:/data
    env_file:
      ./.env
    restart: unless-stopped
    networks:
      - monitor-net
    labels:
      org.label-schema.group: "monitoring"

image_ref: caddy:2.5.0 # image reference used twice in the Dockerfile, once with ${image_ref}-builder, once directly

./caddy/Dockerfile :

ARG image_ref
FROM ${image_ref}-builder AS caddy-build
RUN xcaddy build --with github.com/greenpau/caddy-security
FROM ${image_ref}
COPY --from=caddy-build /usr/bin/caddy /usr/bin/caddy

Caddyfile must exist (content not relevant here):

./caddy/Caddyfile

command :

docker-compose  up --build caddy

Hetzner firewall for outgoing trafic

As noted here :

https://docs.hetzner.com/robot/dedicated-server/firewall/#out-going-tcp-connections

make sure to include a rule in your hetzner Robot firewall / firewall templates if you want to connect to the outerworld. For instance, without the "outgoing" line in my setup, I was not able to perform even a apt-get update.

Hetzner Servers - Robot Firewall / rule for outgoing trafic

• Name : outgoing tcp (for example)
• Source IP : N/A
• Destination IP : N/A
• Source port : N/A
• Destination port : 32768-65535
• Protocol : tcp
• TCP Flags : ack

Agile teams : SAFe, unfix, etc.

 https://unfix.work/blog/the-unfix-model -> SAFe concurrent

Cloud storage

 Cloud storages :

* https://teledriveapp.com

 Use with rclone

https://rclone.org/

Proofread a text for styling and readability level.

 https://draftmap.com/

Proofread your text. Catch style issues and common errors with a quick copy and paste.

==> useful for motivation letters for example

Ikea delivery statuses

Since the "next steps" are not necessarily available, to reduce the anxiety of knowing the next step, this is what I could observe as a delivery workflow statuses during an Ikea delivery in january 2022.

Français :

État de la livraison (inverse)

1. Livré
2. En route
3. Received at nearest hub
4. In transit
5. Getting ready to send
6. Picking completed
7. Picking started
8. En attente d'être cueilli
9. Order received

English :

Delivery status (reverse)

1. Delivered
2. On its Way
3. Received at nearest hub
4. In transit
5. Getting ready to send
6. Picking completed
7. Picking started
8. Waiting to be picked
9. Order received