Hi Nnamdi,

Thank you for bringing that issue to our attention. The Py-DEME's building pipeline is not stable on Windows at this moment.  We suggest you try to build from source or use WSL .

We will likely to bring up a conda package for PyDEME for Windows to make this process much easier this week.

If you intend to reproduce the results that you asked Harry for in another email chain, https://groups.google.com/g/projectchrono/c/fWYnvZKkT4g , Py-DEME is not required and you can just follow the instruction in Harry's github.

I will keep you posted on Py-DEME's Windows conda package.

Best,

Bocheng Zou

On 8/4/25 19:20, 'Nnamdi Chikere' via ProjectChrono wrote:
Thank you so much for your replies.
@Bocheng, I created an environment following the steps you outlined and from the GitHub page to install the Py-DEME I followed these steps

conda install cmake
pip3 install DEME

 I got these errors.
(chrono_test2) conda install cmake
Channels:
 - conda-forge
 - defaults
Platform: win-64
Collecting package metadata (repodata.json): done
Solving environment: done

  cmake              conda-forge/win-64::cmake-4.0.3-hff78f93_0
  libuv              conda-forge/win-64::libuv-1.51.0-hfd05255_1


Proceed ([y]/n)? y
Downloading and Extracting Packages:
Preparing transaction: done
Verifying transaction: done
Executing transaction: done

(chrono_test2) pip3 install DEME
Collecting DEME
  Using cached deme-2.1.2.tar.gz (6.9 MB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... error
  error: subprocess-exited-with-error

  × Getting requirements to build wheel did not run successfully.
  │ exit code: 1
  ╰─> [33 lines of output]
      Traceback (most recent call last):
        File "C:\Users\chike\anaconda3\envs\chrono_test2\Lib\site-packages\pip\_vendor\pyproject_hooks\_in_process\_in_process.py", line 389, in <module>
          main()
        File "C:\Users\chike\anaconda3\envs\chrono_test2\Lib\site-packages\pip\_vendor\pyproject_hooks\_in_process\_in_process.py", line 373, in main
          json_out["return_val"] = hook(**hook_input["kwargs"])
                                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "C:\Users\chike\anaconda3\envs\chrono_test2\Lib\site-packages\pip\_vendor\pyproject_hooks\_in_process\_in_process.py", line 137, in get_requires_for_build_wheel
          backend = _build_backend()
                    ^^^^^^^^^^^^^^^^
        File "C:\Users\chike\anaconda3\envs\chrono_test2\Lib\site-packages\pip\_vendor\pyproject_hooks\_in_process\_in_process.py", line 70, in _build_backend
          obj = import_module(mod_path)
                ^^^^^^^^^^^^^^^^^^^^^^^
        File "C:\Users\chike\anaconda3\envs\chrono_test2\Lib\importlib\__init__.py", line 90, in import_module
          return _bootstrap._gcd_import(name[level:], package, level)
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "<frozen importlib._bootstrap>", line 1387, in _gcd_import
        File "<frozen importlib._bootstrap>", line 1360, in _find_and_load
        File "<frozen importlib._bootstrap>", line 1310, in _find_and_load_unlocked         File "<frozen importlib._bootstrap>", line 488, in _call_with_frames_removed
        File "<frozen importlib._bootstrap>", line 1387, in _gcd_import
        File "<frozen importlib._bootstrap>", line 1360, in _find_and_load
        File "<frozen importlib._bootstrap>", line 1331, in _find_and_load_unlocked
        File "<frozen importlib._bootstrap>", line 935, in _load_unlocked
        File "<frozen importlib._bootstrap_external>", line 999, in exec_module         File "<frozen importlib._bootstrap>", line 488, in _call_with_frames_removed         File "C:\Users\chike\AppData\Local\Temp\pip-build-env-pw8idr9h\overlay\Lib\site-packages\setuptools\__init__.py", line 17, in <module>
          import setuptools.version
        File "C:\Users\chike\AppData\Local\Temp\pip-build-env-pw8idr9h\overlay\Lib\site-packages\setuptools\version.py", line 1, in <module>
          import pkg_resources
        File "C:\Users\chike\AppData\Local\Temp\pip-build-env-pw8idr9h\overlay\Lib\site-packages\pkg_resources\__init__.py", line 2163, in <module>
          register_finder(pkgutil.ImpImporter, find_on_path)
                          ^^^^^^^^^^^^^^^^^^^
      AttributeError: module 'pkgutil' has no attribute 'ImpImporter'. Did you mean: 'zipimporter'?
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error

× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> See above for output.

note: This error originates from a subprocess, and is likely not a problem with pip.


Are there separate steps for installing on Windows?


Best regards,
Nnamdi
On Monday, August 4, 2025 at 2:45:09 PM UTC-4 [email protected] wrote:

    Hi Dan and Nnamdi,

    To add up, since the FSI and VSG support is not yet merged into
    the main branch, if you want to use the PyChrono with FSI / VSG to
    simulate granular terrain in addition to DEME, you need to use our
    special FSI version rather than the regular version I posted in
    previous email. The special FSI version can be installed via the
    following command in a NEW environment:

    conda create -n chrono_test "python<3.13" -c conda-forge
    conda install bochengzou::pychrono -c bochengzou -c nvidia -c
    dlr-sc -c conda-forge

    Best,

    Bocheng


    On 8/4/25 18:24, 'Dan Negrut' via ProjectChrono wrote:

    That functionality for running granular problems from python: see
    pyDEME, https://github.com/projectchrono/DEM-Engine
    
<https://urldefense.com/v3/__https://github.com/projectchrono/DEM-Engine__;!!Mak6IKo!PkKSZCuBiSh-FgdG1GZVwOgPEWrn62SHqzHo482EL_A5V21Isb_oAn9S5AMaFqcONBr_5uh8rK27fuyFYz0y7JL9Uuc2CA$>.


    We’ll probably have one integrated way to install everything
    (chrono & DEM support) coming up in the very near future – next
    three months, most likely. That’ll be through conda forge, a one
    line command, hopefully.

    Dan

    ---------------------------------------------

    Bernard A. and Frances M. Weideman Professor

    NVIDIA CUDA Fellow

    Department of Mechanical Engineering

    Department of Computer Science

    University of Wisconsin - Madison

    4150ME, 1513 University Avenue

    Madison, WI 53706-1572

    608 772 0914

    http://sbel.wisc.edu/ <http://sbel.wisc.edu/>

    http://projectchrono.org/
    
<https://urldefense.com/v3/__http://projectchrono.org/__;!!Mak6IKo!PkKSZCuBiSh-FgdG1GZVwOgPEWrn62SHqzHo482EL_A5V21Isb_oAn9S5AMaFqcONBr_5uh8rK27fuyFYz0y7JLqDzYZVw$>


    ---------------------------------------------

    *From:*'Nnamdi Chikere' via ProjectChrono
    <[email protected]>
    *Sent:* Monday, August 4, 2025 1:14 PM
    *To:* ProjectChrono <[email protected]>
    *Subject:* Re: [chrono] SDL2 Library Error while running PyChrono

    Thank you very much. Adding the "/" character resolved the issue.
    Does this version include the capability to simulate granular
    systems on Windows using Python?

    Best regards,

    Nnamdi

    On Monday, August 4, 2025 at 2:07:48 PM UTC-4 [email protected] wrote:

        Hi Nnamdi,

        Thank you for the follow up. Yes, on Apr 27, 2025, we renamed
        SetPlane to SetReferenceFrame. The details can be found at
        
https://github.com/projectchrono/chrono/commit/59e3cb4ba24dbb258aa1543a971507a7d0bf2689
        
<https://urldefense.com/v3/__https:/github.com/projectchrono/chrono/commit/59e3cb4ba24dbb258aa1543a971507a7d0bf2689__;!!Mak6IKo!NTQLCak0Iwl-Hfht85Jhg4qWkG-A7VWM6pEEbrx0f8_cvW7ySAQlRFoQ1N0NTjfNyeBXHkTouURQJFrnTRiy0LLg6XM$>

        For the "Cannot open colormap data file
        
C:/Users/chike/Box/TurtleRobotExperiments/Sea_Turtle_Robot_AI_Powered_Simulations_Project/NnamdiFiles/mujocotest1/chrono/data../data/colormaps/jet-table-float-0512.csv"
        issue, did you put a "/" character at the end of your
        "chrono.SetChronoDataPath()" call? For example, you need to
        use
        
chrono.SetChronoDataPath("C:/Users/chike/Box/TurtleRobotExperiments/Sea_Turtle_Robot_AI_Powered_Simulations_Project/NnamdiFiles/mujocotest1/chrono/data/")
        instead
        of 
chrono.SetChronoDataPath("C:/Users/chike/Box/TurtleRobotExperiments/Sea_Turtle_Robot_AI_Powered_Simulations_Project/NnamdiFiles/mujocotest1/chrono/data")

        Once you applied that fix, could you please update on if the
        window crash issue gets resolved?

        Thank you very much!

        Best,

        Bocheng Zou

        On 8/4/25 17:58, 'Nnamdi Chikere' via ProjectChrono wrote:

            Hi Bocheng,

            It now works, but it broke certain parts of my code.
            Seems some of the API and syntax have changed in this
            version. I noticed changes in the SCM

              terrain =veh.SCMTerrain(sys)

            /# rotate plane/

            terrain.SetReferenceFrame(chrono.ChCoordsysd(

                    chrono.ChVector3d(0, scm_plane_y, 0),

            chrono.QuatFromAngleX(-math.pi /2)

                ))

            /# Previous version used:/

            terrain.SetPlane(chrono.ChCoordsysd(

                    chrono.ChVector3d(0, scm_plane_y, 0),

            chrono.QuatFromAngleX(-math.pi /2))

                )

            Upon updating to the new version, I am now faced with a
            new error when running the deformable soil ...

            Cannot open colormap data file
            
C:/Users/chike/Box/TurtleRobotExperiments/Sea_Turtle_Robot_AI_Powered_Simulations_Project/NnamdiFiles/mujocotest1/chrono/data../data/colormaps/jet-table-float-0512.csv
            I have the data path correctly specified at the top of my
            code using the chrono.SetChronoDataPath()

            And upon contact with the ground, the window crashes. Do
            you happen to have any fixes for this? Also, are there
            any other changes to the syntax?

            Best regards,

            Nnamdi

            On Friday, August 1, 2025 at 10:17:21 PM UTC-4
            [email protected] wrote:

                Hi Nnamdi,

                I hope you're doing well.

                We're excited to share that we've refactored the
                Conda build pipeline and released updated
                distributions of PyChrono with improved
                cross-platform compatibility, which is likely to
                resolve the issue you encountered.

                To try out the latest release, please create a new
                environment and run the following commands (note that
                the installation command on the website is now oudated):

                conda create -n chrono_test python=3.12 -c conda-forge

                conda install pychrono -c projectchrono -c dlr-sc -c
                conda-forge

                Please let us know if there are any remaining issues.

                Best,

                Bocheng Zou

                On 7/31/25 00:48, Bocheng Zou wrote:

                    Hi Nnamdi,

                    Thank you for providing the information. The
                    Windows conda build for PyChrono is having know
                    issues recently. We are aware of that and it's
                    expected to be fixed within the week. If you are
                    in urgent need of PyChrono, I suggest you build
                    from scratch using cmake (Method A) or use
                    PyChrono's conda distribution on Linux.

                    I will keep you posted once the issue in the
                    Windows conda distribution is fixed.

                    Best,

                    Bocheng Zou

                    On 7/31/25 00:45, 'Nnamdi Chikere' via
                    ProjectChrono wrote:

                        Hello Bocheng,

                        Thank you for reply.

                        I installed PyChrono via method C. PyChrono
                        through Conda (ref:
                        https://api.projectchrono.org/pychrono_installation.html
                        
<https://urldefense.com/v3/__https:/api.projectchrono.org/pychrono_installation.html__;!!Mak6IKo!MLRxot5akRpE7PKpP5V6eTs6EVAmfOwIgWN8nnv81XgdLQUax6qVtwZPINjM2zrnQxAA_GMxqAg8ScgcDXtHvaj1guZPig$>)

                        For the last step I installed via conda
                        install pychrono-9.0.1-py310_5372.tar.bz2

                        Best regards,

                        Nnamdi

                        On Wednesday, July 30, 2025 at 12:18:25 PM
                        UTC-4 [email protected] wrote:

                            Hi Nnamdi,

                            Thank you for reaching out. I'm Bocheng
                            and I'm a UW-Madison student responsible
                            for PyChrono distributions. Could you
                            please clarify the specific way you
                            install the PyChrono? We currently
                            support three ways of installation on
                            Windows.

                            A. Build from scratch using cmake (ref:
                            
https://api.projectchrono.org/tutorial_install_chrono.html
                            
<https://urldefense.com/v3/__https:/api.projectchrono.org/tutorial_install_chrono.html__;!!Mak6IKo!MLRxot5akRpE7PKpP5V6eTs6EVAmfOwIgWN8nnv81XgdLQUax6qVtwZPINjM2zrnQxAA_GMxqAg8ScgcDXtHvahYwqyiWQ$>)

                            B. Precompiled binaries for Windows (ref:
                            https://projectchrono.org/download/
                            
<https://urldefense.com/v3/__https:/projectchrono.org/download/__;!!Mak6IKo!MLRxot5akRpE7PKpP5V6eTs6EVAmfOwIgWN8nnv81XgdLQUax6qVtwZPINjM2zrnQxAA_GMxqAg8ScgcDXtHvahDjDCVhA$>)

                            C. PyChrono through Conda (ref:
                            
https://api.projectchrono.org/pychrono_installation.html
                            
<https://urldefense.com/v3/__https:/api.projectchrono.org/pychrono_installation.html__;!!Mak6IKo!MLRxot5akRpE7PKpP5V6eTs6EVAmfOwIgWN8nnv81XgdLQUax6qVtwZPINjM2zrnQxAA_GMxqAg8ScgcDXtHvaj1guZPig$>)

                            Could you please specify the way you
                            install the chrono? This will be helpful
                            for us to investigate the issue further.

                            Best,

                            Bocheng Zou

                            On 7/28/25 21:22, 'Nnamdi Chikere' via
                            ProjectChrono wrote:

                                Hello,

                                I have recently been faced with an
                                error whenever I try to run any
                                Python programs in PyChrono. Has
                                anyone encountered this before? I use
                                Visual Studio Code and Pychrono 9.0.1
                                on a Windows PC. I followed all the
                                steps for installing Pychrono in a
                                virtual environment. I have tried
                                uninstalling and reinstalling, but it
                                hasn't helped. Everything worked fine
                                in the same env, this error just
                                appeared suddenly. Please, I would
                                like some advice on this.

                                Best regards

                                --
                                You received this message because you
                                are subscribed to the Google Groups
                                "ProjectChrono" group.
                                To unsubscribe from this group and
                                stop receiving emails from it, send
                                an email to
                                [email protected].
                                To view this discussion visit
                                
https://groups.google.com/d/msgid/projectchrono/1f41206d-20f1-48dd-bd2e-73c48d2665fbn%40googlegroups.com
                                
<https://urldefense.com/v3/__https:/groups.google.com/d/msgid/projectchrono/1f41206d-20f1-48dd-bd2e-73c48d2665fbn*40googlegroups.com?utm_medium=email&utm_source=footer__;JQ!!Mak6IKo!J5kXNaPEjXw_OFyqXzUyRfxbYeeLeX3B6PUJwtVXHkPAWJRTx8v6iqVLxYyv7WFxY5Kc7ZNgBvU-1EVwmWr-lIlB3LWUZw$>.

                        --
                        You received this message because you are
                        subscribed to the Google Groups
                        "ProjectChrono" group.
                        To unsubscribe from this group and stop
                        receiving emails from it, send an email to
                        [email protected].
                        To view this discussion visit
                        
https://groups.google.com/d/msgid/projectchrono/8b5c5803-6308-461f-a84b-24188f960344n%40googlegroups.com
                        
<https://urldefense.com/v3/__https:/groups.google.com/d/msgid/projectchrono/8b5c5803-6308-461f-a84b-24188f960344n*40googlegroups.com?utm_medium=email&utm_source=footer__;JQ!!Mak6IKo!MLRxot5akRpE7PKpP5V6eTs6EVAmfOwIgWN8nnv81XgdLQUax6qVtwZPINjM2zrnQxAA_GMxqAg8ScgcDXtHvaghyluLsg$>.

-- You received this message because you are subscribed to
            the Google Groups "ProjectChrono" group.
            To unsubscribe from this group and stop receiving emails
            from it, send an email to [email protected].

            To view this discussion visit
            
https://groups.google.com/d/msgid/projectchrono/75f5b824-28fe-44ae-95eb-8d765a9262d0n%40googlegroups.com
            
<https://urldefense.com/v3/__https:/groups.google.com/d/msgid/projectchrono/75f5b824-28fe-44ae-95eb-8d765a9262d0n*40googlegroups.com?utm_medium=email&utm_source=footer__;JQ!!Mak6IKo!IRf7felC0zthyzFHiWt0Ao1tNXGtN4de2KoYPYzS_GKYjI14ZpqR7hrjIDLet90eR9_pbikVqkrEHniADSvqg078c5z7OQ$>.

-- You received this message because you are subscribed to the
    Google Groups "ProjectChrono" group.
    To unsubscribe from this group and stop receiving emails from it,
    send an email to [email protected].
    To view this discussion visit
    
https://groups.google.com/d/msgid/projectchrono/49716d7c-be19-4618-9045-c70c9a52487cn%40googlegroups.com
    
<https://urldefense.com/v3/__https:/groups.google.com/d/msgid/projectchrono/49716d7c-be19-4618-9045-c70c9a52487cn*40googlegroups.com?utm_medium=email&utm_source=footer__;JQ!!Mak6IKo!NTQLCak0Iwl-Hfht85Jhg4qWkG-A7VWM6pEEbrx0f8_cvW7ySAQlRFoQ1N0NTjfNyeBXHkTouURQJFrnTRiyS8Y4SOY$>.

-- You received this message because you are subscribed to the
    Google Groups "ProjectChrono" group.
    To unsubscribe from this group and stop receiving emails from it,
    send an email to [email protected].
    To view this discussion visit
    
https://groups.google.com/d/msgid/projectchrono/DM8PR06MB7703828DACB191C6919A9F5CB123A%40DM8PR06MB7703.namprd06.prod.outlook.com
    
<https://urldefense.com/v3/__https://groups.google.com/d/msgid/projectchrono/DM8PR06MB7703828DACB191C6919A9F5CB123A*40DM8PR06MB7703.namprd06.prod.outlook.com?utm_medium=email&utm_source=footer__;JQ!!Mak6IKo!PkKSZCuBiSh-FgdG1GZVwOgPEWrn62SHqzHo482EL_A5V21Isb_oAn9S5AMaFqcONBr_5uh8rK27fuyFYz0y7JKMawPNlQ$>.

--
You received this message because you are subscribed to the Google Groups "ProjectChrono" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/projectchrono/8e4d2b37-ac26-40ef-9809-8001e50478e4n%40googlegroups.com <https://urldefense.com/v3/__https://groups.google.com/d/msgid/projectchrono/8e4d2b37-ac26-40ef-9809-8001e50478e4n*40googlegroups.com?utm_medium=email&utm_source=footer__;JQ!!Mak6IKo!MOydWjt1aBVCF5R51ctIZ4Gnx9H3o4RyWw3B_S1FiLZphAAGyLn93MaPChshcleJc-dsRuB3Ojp2aK9O88KmGIsXSMsTLg$>.

--
You received this message because you are subscribed to the Google Groups 
"ProjectChrono" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/d/msgid/projectchrono/88b464cc-5d12-45c4-b77d-237a429b28ec%40wisc.edu.

Reply via email to