-
Notifications
You must be signed in to change notification settings - Fork 65
Specify requirements #352
Copy link
Copy link
Open
Labels
DevOpsTesting, deployment, automationTesting, deployment, automationbreakingBreaking change (CLI, input & output files)Breaking change (CLI, input & output files)comp-DocsRelated to documentationRelated to documentationmaintainabilitySimplifies further code development (standardization, robustness)Simplifies further code development (standardization, robustness)pri-MediumWorth assigning to a milestoneWorth assigning to a milestone
Milestone
Metadata
Metadata
Assignees
Labels
DevOpsTesting, deployment, automationTesting, deployment, automationbreakingBreaking change (CLI, input & output files)Breaking change (CLI, input & output files)comp-DocsRelated to documentationRelated to documentationmaintainabilitySimplifies further code development (standardization, robustness)Simplifies further code development (standardization, robustness)pri-MediumWorth assigning to a milestoneWorth assigning to a milestone
Type
Fields
Give feedbackNo fields configured for Task.
Specify requirements of ADDA in machine-readable format, e.g.
requirements.txt. It is very relevant for semantic version control and packaging of ADDA. However, there are several complications (some of them mentioned in #282):requirements are very heterogeneous:
Makefileprobably requires specific compilers, but is rather flexible to work in automated workflow with proper setting of environmental variables.requirements depend on the compilation mode (many dependencies are optional):
seq,mpi,ocl) have specific requirementsOCL_BLAS)for some dependency we do not know the minimum supported version
To conclude, we need to study best practices before starting working on it.