dangunter

import sys, time
from netlogger.analysis.workflow.stampede_statistics import *
st = StampedeStatistics("sqlite:///gp-0.stampede.db")
w="89a25dd1-e8ae-4f15-9dea-367bbf598779"
st.initialize(w)
sys.stdout.write("method,time\n")
for fn in filter(lambda s: s.startswith('get_'), dir(st)):
    sys.stdout.write("{},".format(fn))
    sys.stdout.flush()
    t = time.time()

dangunter

gp-0.stampede.db

method,time
get_condor_q_time,0.000005
get_descendant_workflow_ids,0.001646
get_failed_job_instances,0.000004
get_invocation_by_time,2.845388
get_invocation_by_time_per_host,4.467101
get_invocation_info,0.000007

dangunter

"""
Task graph
==========
Some toy code to play with the aspects
of the task-graph problem. Note that this is
all in-memory, but really want to implement so it
can directly manipulate mongodb data.

Initial problem statement
--------------------------

dangunter

"""
Given x,y,z MIDs, dump the data values in range a to b to a CSV
"""
import argparse
import os
import sys
#
import pymongo
from pymongo_mr import base as mr_base

dangunter

## Generate graph of run history

Generating the graph requires 2 scripts

1) A Python script to extract the dates of each compound from the
database. Replace DB, USER and PASSWORD below with appropriate values:

    ./mg_run_history.py DB USER PASSWORD --port 27018 > runs.csv

dangunter

#!/usr/bin/env python
"""
Generate many fireworks workflows.
"""
import argparse
import os
import sys

def main():
    p = argparse.ArgumentParser(description="Generate fireworks")

dangunter

dangunter

Conference

11th IEEE International Conference on eScience (08/31-09/04/2015 in Munich)

'i') Full Paper

submit for main conference by March 23rd (camera-ready & reviewed by June 7), OR

'ii') Short Paper

submit for "Works in progress" workshop due in camera-ready form on June 21, and accompany with poster due on May 20

Title

'Development of the Materials Project's

dangunter

AJAX
AMR
AngularJS
Apache HTTPD
Assembly
BLAST - Basic Local Alignment Search Tool
C/C++
CGI
cloud computing
CSS

dangunter

# Weaknesses

* Sharing/granularity
* Versioning
* Narratives together with bio objs
* References
  - shock vs. W.S. vs. CDS
  - permissions relaxed on refs
  - all refs hierarchical/one-way
  - data copies may not be complete