Add conditionally included submodules

Open
#26 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Domain
build-system

Research direction

Start with common/Makefile and the task-specific makefiles described in the issue, then trace how the common rules and the _footer are currently included. Define the conditional variables for profiling data, features, task type, and permutation evaluation, and consider the work done when each collection of evaluation metrics can be toggled per task.

Written by the indexing model from the issue text.

Description

Came up with this in #25

Collect common rules into a separate _footer which is conditionally included based on the value of a variable in the task-specific makefile. In common/Makefile we could have something like:

PROFILE_RAW_DATA := FALSE 
PROFILE_FEAUTRES := TRUE

Downstream, we could have stuff like:

REGRESSION_TASK := FALSE
CLASSIFICATION_TASK := TRUE
PERMUTATION_OK := TRUE

to turn collections of evaluation metrics on or off.

Dominant language
HTML
Stars
3
Forks
0
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dmarx/make_for_datascience

All issues in dmarx/make_for_datascience

Similar issues

More Build System issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.