Page History
...
| Feature/capability | Importance for MVP (must, should, nice) | Difficulty to deliver in MVP (high, medium,low) | Comments | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| user-friendly APIs | should | high | This is at least for a quick/dirty run. I think this This might be similar to what Nimish Hathi mentioned. This concern is also including how data and processed data are encapsulated in variables inside the working environment (e.g., Jupyter). For example, considering the aXe outputs (check this ticket in Jira for some info
| ||||||||
| modularity | must | This would be useful especially when we think of extendability either adding new grism definition from different facilities, or user customized objects from base classes. | |||||||||
| Interactive GUI | nice | Interactive graphic user interface will help users to quickly examine visually. | |||||||||
| documentation | must | This is important, as we all can agree  | |||||||||
| minimal code comment standard | should | We should discuss about what would be the minimal requirement for code commenting. Have these requirements noted down, and make sure that all codes complied to the minimal standard before accepting any push to the main code body. We might assign someone specifically to go through all codes and check for the compliance. | |||||||||
| Tutorial / cookbook | must | This should explain itself how it import it is. | |||||||||
...
