Spectral film simulations in ART

Software ART
61

Hey @Topoldo, great work with the documentation! Didn’t expect the update to change any compatibility, but I am happy to see that @agriggio and @sguyader managed to run it.

I am currently working on the profile creation side, and hopefully I will update the log-sensitivities of all the profiles with a more sound density unmixing procedure. I don’t expect big changes, but they should become “more correct”, in theory at least. :slightly_smiling_face:

62

@arctic: I need to update the documentation because of changes you made (essentially removing the requirements.txt file).
Beside, as I reported above, if I try to load an image inside agx-emulsion GUI => napari using uv(x) - and not using ART - I couldn’t since an old version of agx-emulsion. But this is the ART forum, so I stop here myself.

Regards,
Topoldo

1 Like
63

For me the simplified version of the necessary steps to run the latest agx-amulsion on Linux (Arch in my case) are:

  1. install uv
  2. install python 3.11 by issuing uv python install 3.11
  3. clone the agx-emulsion repo
  4. issuing uvx path/to/local/agx_repo (prepares and installs the packages, and launches the agx-amulsion napari GUI)
  5. edit the command in ART_agx_film.json to uv run --python 3.11 --with-editable path/to/local/agx_repo agx_emulsion_mklut.py --server

HTH

64

Leopoldo, starting from your documentation (thank you for that) I’m currently trying to both update it with the recent changes and with instruction for Linux/MacOS.

1 Like
65

I went back to everything fresh…so I installed ART 1.25.4 on Win11, downloaded the the py and json files to use the film sim pipeline. I put them together in the luts folder in the art program directory.

I downloaded the zip of the agx-emulsion repo

I felt like I was just not getting a path right and likely still this is the case but anyway I made it simple and unzipped that to E:\ and then ran uvx and the GUI fires up and I can edit the test image…so far so good

No matter what I try for the command line in the json file when I go to use it in ART as a lut as described I get the message error reading the file…

I have tried a few versions of this… (including using double back slashes)
“uv run --python 3.11 --with-editable E:\agx-emulsion-main agx_emulsion_mklut.py --server”

uv is in my path and will run if I just type it on the commandline but I have also tried as suggested above to specify the full path for it… still no joy…

Not sure whatelse to try…

66

Do you see any error messages when you type the following command from the command line?

“uv run --python 3.11 --with-editable E:\agx-emulsion-main agx_emulsion_mklut.py --server”

67

I had had that though and tried…I am not at my PC now but I can check later…when I did it it said something about failing to spawn Win32 app or something of that nature…I will re-run it when I get home and provide the exact output from running that…thanks for taking the time to comment…

Edit:

I get this…

image

68

I’ve tried to finish editing the howto initiated by @Topoldo. I found that the uv way doesn’t work easily for every OS, so in my howto I’ve used the regular virtualenv instead. It works for Windows (not the easiest), MacOS and Linux.
It’s now available on ART’s wiki: Spectral film simulations in ART with agx-emulsion | ART raw image processor

69

Thanks I thought the UV way would be easy and I can run the software but maybe it is best to just go back and follow your guide to get it working in ART,.thanks

70

Hi @sguyader and thank you for your work!
While you were updating this HowTo I also have been trying to make ART & Spectral film simulation work together, by using the latest ART and agx-emulsion releases.
In fact with the latest versions of ART & agx-emulsion, I also found quite cumbersome trying to use uv (at least in a Windows environment), so I decided to move to Python, specifically version 3.11.9 for Windows.

At present, my only need to have Python installed is for getting Andrea Volpato’s age-emulsion working with ART and so - in order to avoid using too much space on my PC just for a commited developing tool - I decided to avoid using Python virtualenv.

In these conditions I got a result which was different from your, for what the modification of ART_agx_film.json line 12 was concerned.

In detail, what I did was:

  1. I installed Python and I made sure that:
    C:\Program Files\Python
    and
    C:\Program Files\Python\Scripts
    were in the PATH of environmental variables
  2. Then I downloaded latest agx-emulsion from github as a .zip file and I unzipped it in a local directory, for example:
    C:\stuffs\agx-emulsion
    BTW, users must know that - apparently - the version they can get is still the initial one, ie 0.10-alpha, while this is deeply different from that!
  3. At this point I opened a command shell as admin and typically it was opened in:
    C:\Windows\System32>
  4. So I had to move into:
    C:\stuffs\agx-emulsion>
    and from there I had to execute the command:
    C:\stuffs\agx-emulsion> python -m pip install -e .
  5. By using this procedure agx-emulsion.exe was created inside:
    C:\Program Files\Python\Scripts>
    directory
  6. At this point I had to modify only just a little bit the original line 12 of ART_agx_film.json in order to make ART & age-emulsion work together.
  7. Infact, what I did was to substitute the original line:
    "command" : "python3 agx_emulsion_mklut.py --server",
    with this one:
    "command" : "python.exe agx_emulsion_mklut.py --server",
    and everything was working.

Please note that I don’t know if this works also by using the Python virtualenv.

Regards,
Leopoldo aka Topoldo

1 Like
71

The advantage of using virtualenv is that if you have Python installed system-wide with a recent version such as 3.14, you can keep it and still install Python 3.11 in the isolated environment provided by virtualenv.
But that’s the theory, because when I tried on Windows with Python 3.14 installed system-wide, I couldn’t install Python 3.11 in virtualenv (I got errors that I was unable to get passed). So in the end, for Windows I still suggest to install Python 3.11 system-wide and then you don’t need to use virtualenv, but I still wanted to make the howto “uniform” with the use of virtualenv for the 3 main operating systems.

72

Hi again!

By reading the HowTo I found 3 typos that should be corrected (IMHO):

  1. At the beginning, (Chapter 1: Installing pipx and virtualenv) you wrote:
    “Since agx-emulsion relies on Python, the use of a virtual environment for Python is recommended. Here we will describe how to install and use virtualenv which a fast, cross-platform tool for managing isolated Python environments which allow installing and running different versions of Python.”
    You forgot an “is”:
    “Since agx-emulsion relies on Python, the use of a virtual environment for Python is recommended. Here we will describe how to install and use virtualenv which is a fast, cross-platform tool for managing isolated Python environments which allow installing and running different versions of Python.”

  2. At the beginning of Chapter 2 - Installing and preparing agx-emulsion environment, you wrote:

For Windows:

  • if you use cdm.exe type:

while you should have written:

For Windows:

  • if you use cmd.exe, type:
  1. Lastly, immediately before the beginning of Chapter 3: agx-emulsion integration in ART, you left in the manuscript the title of the previous chapter, ie:
    age-emulsion native GUI
    whose content you completely removed.
    So please, consider to remove also that “title”.

Have the best,
Leopoldo

73

Thank you. That howto became a mess because I first wrote it with uv as the way to install agx-emulsion, then after going through too much trouble with uv I changed to virtualenv but of course I’m not surprised there are typos or mistakes left behind.

74

Hi again!
I saw you have corrected almost everything except at the beginning of Chapter 2 - Installing and preparing agx-emulsion environment, where you wrote:

For Windows:

  • if you use cdm.exe type:

while you should have written:

For Windows:

  • if you use cmd.exe, type:

Regards,
Topoldo

1 Like