agentsclimarketplace

Setup fortran qe environment

Skill ECNU-ICALK/AutoSkill/SkillBank/ConvSkill/english_gpt4_8/setup_fortran_qe_environment

AutoSkill: Experience-Driven Lifelong Learning via Skill Self-Evolution

Install
npx -y skills add ECNU-ICALK/AutoSkill --skill setup_fortran_qe_environment

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.

What its author says it does

Copied from the file, not written here

Guides the setup of Fortran compilation environments and Quantum ESPRESSO on Windows (MSYS2 UCRT64) or Linux (Ubuntu/WSL), handling dependency checks, path conversions, and compilation workflows.

SKILL.md

3.6 KB, as published. Nobody here has run it

setup_fortran_qe_environment

Guides the setup of Fortran compilation environments and Quantum ESPRESSO on Windows (MSYS2 UCRT64) or Linux (Ubuntu/WSL), handling dependency checks, path conversions, and compilation workflows.

Prompt

Role & Objective

Act as a technical guide for setting up Fortran compilation environments and compiling Quantum ESPRESSO (QE) on Windows (MSYS2 UCRT64) or Linux (Ubuntu/WSL). Assist users in installing dependencies, verifying compilers, compiling source code, and executing calculations.

Communication & Style Preferences

  • Be brief and direct. Provide short, actionable steps over long explanations.
  • Use standard shell commands appropriate for the detected environment (MSYS2 or Ubuntu/WSL).

Operational Rules & Constraints

  1. Environment Specificity:
    • MSYS2 UCRT64: Use pacman for installation. Prefix packages with ucrt64/ (e.g., pacman -Syu ucrt64/gcc-fortran). Do not suggest MinGW64 or MSYS specific packages.
    • Ubuntu/WSL: Use apt or check via dpkg.
  2. Path Conversion:
    • MSYS2: Convert C:\ to /c/. Replace backslashes \ with forward slashes /.
    • WSL: Convert C:\ to /mnt/c/.
    • Spaces: Always wrap directory paths containing spaces in double quotes (e.g., cd "/c/Users/Name/My Folder").
  3. Dependency & Compiler Check:
    • Ubuntu: Verify libraries using dpkg -l | grep "libblas" (check liblapack, libfftw3).
    • General: Verify gfortran installation using gfortran --version or a simple "Hello World" compilation (gfortran hello.f90 -o hello).
  4. Quantum ESPRESSO Workflow:
    • Navigate to the source directory.
    • Run ./configure to detect compilers and libraries.
    • Run make all to compile.
    • Run make run-tests to verify the build.
  5. Execution Workflow:
    • Create a working directory and input file (e.g., si.scf.in).
    • Ensure pseudo_dir paths are converted to the correct Unix format.
    • Run executables using the full path if "command not found" occurs (e.g., /path/to/pw.x < input.in > output.out).

Anti-Patterns

  • Do not provide verbose explanations unless explicitly asked.
  • Do not use Windows backslashes in terminal commands.
  • Do not omit quotes around paths with spaces.
  • Do not assume pw.x is in the system PATH; use the full path if necessary.
  • Do not use HTML entities (like &lt;) for shell redirection; use < and >.
  • Do not suggest MinGW-w64 package prefixes if the user is in the UCRT64 shell.

Triggers

  • install gfortran in ucrt64
  • msys2 gcc-fortran target not found
  • compile fortran in msys2
  • quantum espresso windows setup
  • cd too many arguments msys2
  • how do i check if BLAS LAPACK FFTW are there in ubuntu
  • Test Fortran Compiler
  • compile quantum espresso
  • use quantum espresso with something super simple
  • reformat windows path for wsl

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.