Bryan Hilbert

So it seems like it comes down to some issue with running `conda env export` when called from the webpage?

The subprocess is called by log_info(), which is called when the msata run() function is called. My expectation is that this should just be running `conda env export` on the...

Another piece to add to the puzzle: I checked the log file for yesterday's dark monitor run on the test server. The environment was successfully retrieved there. So what's different...

This was in a recent log file, just prior to the environment problem: ``` WARNING: [Errno 2] No such file or directory: 'conda': 'conda' ``` It's not clear to me...

The only difference I can think of between the TA monitors and the other monitors is that the others are all called on the command line in our crontab, while...

- [x] Line 246 of monitor_views should be module = 'msata_monitor' rather than module = 'msata_monitor.py'

I think there's just one more change this needs and then it'll be ready to go. I think the best solution at the moment to get around the logging error...

@Skyhawk172 I missed your talk this week, but others on JWQL saw it and wondered if tools for tracking PSF metrics would be something you'd want to implement in JWQL.

None of the SI teams are doing anything like this at the moment, although NIRCam has expressed interest recently in a photometric stability monitor, so there may be some overlap...

@mfixstsci I'm happy with the local testing results for this one, so it's ready for review.