ISISNeutronMuon / ISISNeutronMuon/MDANSE

[ENHANCEMENT] Grey out jobs that can't be run for the selected trajectory.

Open
#555 0 comments 0 reactions 0 assignees View on GitHub
enhancement good first issue
Dominant language
Python
Stars
29
Forks
8
Avg merge
2d 12h
Merged PRs (30d)
9

Description

**Is your feature request related to a problem? Please describe.**
Some trajectories will not work for specific jobs. For example, when a trajectory does not have a unit cell a density job will fail. Currently, we allow the user to run the job but it will crash and give the user an error message about why the job failed.

**Describe the solution you'd like**
We should be able to determine beforehand that the job will crash. Let's gray out the job so that it can't be run when the trajectories don't have the required properties and provide some information to the user about why the trajectory can't run that job.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by tracing the job-selection UI and the validation or execution paths that determine whether a trajectory has the properties a job requires. Identify the required properties for each job, then verify that incompatible jobs are disabled and that the user sees why; the issue names no files or tests, so locating those entry points is part of the work.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
desktop, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.