Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

I am having trouble installing esa-snappy on windows 10.I have python 3.10.6 #1

Open
saqibzia-dev opened this issue Jan 18, 2024 · 1 comment

Comments

@saqibzia-dev
Copy link

saqibzia-dev commented Jan 18, 2024

I have installed latest snap software from:
https://step.esa.int/main/download/snap-download/
Note: I didnot clone the esa-snappy git repo I directly ran it when I installed snap
Then I ran this command:
1.cd C:\Program Files\snap\bin

  1. .\snappy-conf.bat D:\crop_health_latest\sentinel_automatic_download\Scripts\python.exe D:\crop_health_latest\sentinel_automatic_download\Lib\site-packages\

when I first ran it I got error code 10 saying no so I downloaded wheels from jpy pypi for python 3.10
here is the wheels file name : jpy-0.15.0-cp310-cp310-win_amd64.wheel

Then I copied this to my python virtual env on this path:
D:\crop_health_latest\sentinel_automatic_download\Lib\site-packages\snappy

Then I ran this command again:
.\snappy-conf.bat D:\crop_health_latest\sentinel_automatic_download\Scripts\python.exe D:\crop_health_latest\sentinel_automatic_download\Lib\site-packages\

Now its giving me error code 30:
here is the snappy_util.log
################start of log######################
INFO: Installing from Java module 'C:\Program Files\snap\snap\modules\org-esa-snap-snap-python.jar'
INFO: Installing jpy...
INFO: Unzipping 'D:\crop_health_latest\sentinel_automatic_download\Lib\site-packages\snappy\jpy-0.15.0-cp310-cp310-win_amd64.whl'
INFO: Configuring jpy...
INFO: jpy Python API configuration written to 'D:\crop_health_latest\sentinel_automatic_download\Lib\site-packages\snappy\jpyconfig.py'
INFO: jpy Java API configuration written to 'D:\crop_health_latest\sentinel_automatic_download\Lib\site-packages\snappy\jpyconfig.properties'
INFO: Configuring snappy...
INFO: snappy configuration written to 'D:\crop_health_latest\sentinel_automatic_download\Lib\site-packages\snappy\snappy.ini'
INFO: Importing snappy for final test...
ERROR: Configuration failed with exit code 30

###############end of log ##############

.\snappy-conf.bat D:\crop_health_latest\sentinel_automatic_download\Scripts\python.exe D:\crop_health_latest\sentinel_automatic_download\Lib\site-packages\ The launcher has determined that the parent process has a console and will reuse it for its own console output. Closing the console will result in termination of the running program. Use '--console suppress' to suppress console output. Use '--console new' to create a separate console window. Configuring SNAP-Python interface... java.io.IOException: Python configuration failed. Command [D:\crop_health_latest\sentinel_automatic_download\Scripts\python.exe .\snappyutil.py --snap_home "C:\Program Files\snap" --java_module "C:\Program Files\snap\snap\modules\org-esa-snap-snap-python.jar" --force --log_file .\snappyutil.log --jvm_max_mem 10G --java_home "C:\Program Files\snap\jre\jre" --req_arch amd64] failed with return code 30. Please check the log file 'D:\crop_health_latest\sentinel_automatic_download\Lib\site-packages\snappy\snappyutil.log'. at org.esa.snap.python.PyBridge.configureJpy(PyBridge.java:232) at org.esa.snap.python.PyBridge.installPythonModule(PyBridge.java:149) at org.esa.snap.rcp.cli.SnapArgsProcessor.processPython(SnapArgsProcessor.java:103) at org.esa.snap.rcp.cli.SnapArgsProcessor.process(SnapArgsProcessor.java:49) at org.netbeans.modules.sendopts.DefaultProcessor.process(DefaultProcessor.java:202) at org.netbeans.spi.sendopts.Option$1.process(Option.java:387) at org.netbeans.api.sendopts.CommandLine.process(CommandLine.java:317) at org.netbeans.modules.sendopts.HandlerImpl.execute(HandlerImpl.java:62) at org.netbeans.modules.sendopts.Handler.cli(Handler.java:69) at org.netbeans.CLIHandler.notifyHandlers(CLIHandler.java:234) at org.netbeans.core.startup.CLICoreBridge.cli(CLICoreBridge.java:82) at org.netbeans.CLIHandler.notifyHandlers(CLIHandler.java:234) at org.netbeans.CLIHandler$1.exec(CLIHandler.java:268) at org.netbeans.CLIHandler.finishInitialization(CLIHandler.java:447) at org.netbeans.MainImpl.finishInitialization(MainImpl.java:256) at org.netbeans.Main.finishInitialization(Main.java:92) at org.netbeans.core.startup.Main.start(Main.java:316) at org.netbeans.core.startup.TopThreadGroup.run(TopThreadGroup.java:123) at java.lang.Thread.run(Thread.java:748) Python configuration error: Python configuration failed. Command [D:\crop_health_latest\sentinel_automatic_download\Scripts\python.exe .\snappyutil.py --snap_home "C:\Program Files\snap" --java_module "C:\Program Files\snap\snap\modules\org-esa-snap-snap-python.jar" --force --log_file .\snappyutil.log --jvm_max_mem 10G --java_home "C:\Program Files\snap\jre\jre" --req_arch amd64] failed with return code 30. Please check the log file 'D:\crop_health_latest\sentinel_automatic_download\Lib\site-packages\snappy\snappyutil.log'.

@dolaf
Copy link
Collaborator

dolaf commented Jan 19, 2024

Dear Saqib,

you are trying to use Python 3.10 with SNAP v9 and an appropriate jpy wheel downloaded for your Windows platform. In principle you did everything right, but unfortunately it turned out that using Python >= 3.7 with this approach is not fully reliable. There are lots of possible combinations regarding jpy versions, Python versions and operating systems, and not all of them seem to work properly. For this reason we strongly recommend to use Python <= 3.6 with SNAP <= v9. See https://senbox.atlassian.net/wiki/x/BQAIAw.

To overcome these issues, the next SNAP release v10 will provide a fully revised Python support. It will come with tested jpy wheels (external download no longer necessary) for all platforms and Python versions up to 3.10. SNAP v10 will be released within the next few weeks. Thank you for your patience.

Best wishes,
Olaf

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants