Coder Social home page Coder Social logo

en-deep's People

Contributors

tuetschek avatar

Stargazers

 avatar

Watchers

 avatar

en-deep's Issues

Bugs in Task reset

Task reset feature should be reviewed, its behavior is sometimes strange (for a 
prefix, it resets the whole plan).

Original issue reported on code.google.com by [email protected] on 9 Jul 2010 at 5:04

Issue warnings on pattern collision

Issue warnings if there may be a pattern collision (one pattern is a
subpattern of another) in order to prevent problems in scenario reruns.

E.g.: file*.txt and file1*.txt exist in two different tasks, but file1*.txt
is produced later. If file1*.txt is already produced and the task that
produces file*.txt gets reset, the pattern expansion includes also
file1*.txt and it may get messy.

Original issue reported on code.google.com by [email protected] on 30 Apr 2010 at 12:22

Add support for local temp-files

There should be some switch with path prefix that will be considered to be 
local, e.g. /tmp. All tasks which have this prefix in their I/O specs and 
depend on each other should then be lined up for computation on the same 
machine.

Original issue reported on code.google.com by [email protected] on 17 Jul 2010 at 8:33

Improve expansion performance

In the current setting, the expanded task is copied along with all the 
dependencies of the original task, which are then removed. This increases 
complexity and reduces performance with more than ca. 10000's of tasks.

Original issue reported on code.google.com by [email protected] on 24 Jul 2010 at 5:48

Create a parse-only option for Process

There should be an option, which, when selected, just parses the scenario file 
and end the whole program. It would be useful just to check for errors in the 
plan file before launching the process.

Original issue reported on code.google.com by [email protected] on 9 Jul 2010 at 5:49

Partial task patterns should be implemented

For a task that outputs a-**.txt, some of which are a-*-x.txt, there is no way 
to capture just the a-*-x.txt in the input of another task. 

There should be something like a-*|-x|.txt, which would depend on a task 
producing a-**.txt, but take only a-*-x.txt as input

Original issue reported on code.google.com by [email protected] on 7 Jul 2010 at 3:52

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.