arcane2graph
Executer arcane en sequentiel avec les options suivantes
-A,export_format=xml,export_output_directory=[path],export_only=true
!!! export_only sert à tuer le processus avant le lancement de la simultation en provoquant une erreur, l'erreur est donc normale.
Convertir les configs .xml extraites via arcane en .json
python merge.py
Note: The merge.py script now handles both XML-to-JSON conversion and database import in a single command. The script automatically:
- Converts XML files from
./xmlto JSON in./arc_json - Merges the JSON data into Neo4j
- Imports AXL export files into Neo4j
Installation & Setup with pip
Quick Start (First Time Only)
- Create a local virtual environment:
python3 -m venv .venv
- Activate it (Linux/Ubuntu Bash):
source .venv/bin/activate
- Install the package:
pip install -e .
Running the Package
After activation (recommended):
source .venv/bin/activate
arcane2graph --help
arcane2graph --xml-path ./xml --json-path ./arc_json --neo4j-password password
Without activation (one-off commands):
./.venv/bin/arcane2graph --help
./.venv/bin/arcane2graph --xml-path ./xml
What This Does
- Creates an isolated
.venv/folder in your project - Installs the package locally without affecting other projects
- Makes the
arcane2graphcommand available - The
-eflag installs in development mode (changes to code take effect immediately)
convertir les .axl en .json via axlstar
axl2ccT4 -l json -o \[output_path\] \[path_to_axl\]/Mahyco.axl
Déploiement docker
docker run \
-d \
-p 7474:7474 -p 7687:7687 \
-v $PWD/data:/data -v $PWD/plugins:/plugins \
--name neo4j-apoc \
-e NEO4J_apoc_export_file_enabled=true \
-e NEO4J_apoc_import_file_enabled=true \
-e NEO4J_apoc_import_file_use__neo4j__config=true \
-e NEO4J_PLUGINS=\[\"apoc\",\"apoc-extended\"\] \
-e NEO4J_AUTH=neo4j/password \
neo4j:5.26
Remplir la BDD
Lancer merge.py qui exécute maintenant les trois étapes :
- Conversion des fichiers XML en JSON
- Fusion des données JSON dans Neo4j
- Import des fichiers AXL export dans Neo4j
Une seule exécution du script suffit.
Arguments de merge.py
python merge.py [OPTIONS]
Options:
--xml-path PATH Path to XML input directory (default: ./xml)
--json-path PATH Path to JSON directory - output of conversion and input for merge (default: ./arc_json)
--skip-convert Skip XML to JSON conversion step (default: false)
--neo4j-uri URI Neo4j connection URI (default: bolt://localhost:7687)
--neo4j-username USERNAME Neo4j username (default: neo4j)
--neo4j-password PASSWORD Neo4j password (default: password)
Exemples
python merge.py --xml-path ./config/xml --json-path ./config/json --neo4j-uri bolt://localhost:7687 --neo4j-username neo4j --neo4j-password password
Interface web
http://localhost:7474/browser/
couple specification instance pour l'option nommée ...
MATCH p=(o: Option {fullName: "Mahyco/boundary-condition"})-[r:SPECIFIES]->()
return p
Couverture de toutes les options
MATCH (o)-[:SPECIFIES]->(n)
WITH apoc.map.clean(properties(n), ['uid'], []) AS props, coalesce(o.fullName, o.name) AS name
UNWIND keys(props) AS key
RETURN name, key, props[key] AS value, count(*) AS count
ORDER BY name, count DESC;
Metadata
Release files for arcane2graph 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| arcane2graph-0.1.0.tar.gz | 17.8 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| arcane2graph-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 24.6 kB
Release files / arcane2graph-0.1.0.tar.gz
| Download URL | arcane2graph-0.1.0.tar.gz |
|---|---|
| Size | 17.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a7de7e778b057f7dc1401d6b0c4be61bf58391386aafc072b53ff95048078ed1
|
|
BLAKE2b-256 checksum How to use checksums |
423dd84a82651ae9c45e3d9626d0ed9f463a9919c69e5672f44525605a677c21
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 2, 2026.
Transparency logRelease files / arcane2graph-0.1.0-py3-none-any.whl
| Download URL | arcane2graph-0.1.0-py3-none-any.whl |
|---|---|
| Size | 6.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9b734bb183fc8321509798ebf4e4b11dc47caf918e7f2cb1d11fd114665f3cc5
|
|
BLAKE2b-256 checksum How to use checksums |
4091153634a17d8e27834a8c5c02a16ad064a7a7989b19ce17fb430d2040c07c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 2, 2026.
Transparency logSecurity for arcane2graph 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for arcane2graph-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 2, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.