|
Project Wiki Asterias wiki pages |
Main /
AsteriasDevelopmentPageMain.AsteriasDevelopmentPage HistoryHide minor edits - Show changes to markup September 08, 2006, at 12:49 PM
by -
Changed lines 32-42 from:
to:
- Python Web Application Frameworks. We have started changing the code of applications to use Pylons. - Parallelization et al.: allow use of other MPI frameworks (MPICH, OpenMPI), improved usage of clusters of SMP machines (Unified Parallel C, MPI + OpenMP) and NetworkSpaces with Sleigh (note that the later can be used with both Python and R). Changed lines 45-48 from:
- Python Web Application Frameworks. What would we gain from using frameworks such as Pylons, TurboGears or any of the other available frameworks (see, e.g., Python's wiki on web programming). Looks like configuration, portability, code reuse, and ease of future developments would all benefit. What are the costs of converting/porting our current code base? to:
Changed lines 54-60 from:
- Parallelization et al.: allow use of other MPI frameworks (MPICH, OpenMPI), improved usage of clusters of SMP machines (Unified Parallel C, MPI + OpenMP) and NetworkSpaces with Sleigh (note that the later can be used with both Python and R). to:
June 19, 2006, at 08:58 AM
by -
Changed lines 35-41 from:
- Python Content Management Systems and Application Frameworks. What would we gain from using frameworks such as Webware, CherryPy, or Karrigell? What about portability? to:
- Python Web Application Frameworks. What would we gain from using frameworks such as Pylons, TurboGears or any of the other available frameworks (see, e.g., Python's wiki on web programming). Looks like configuration, portability, code reuse, and ease of future developments would all benefit. What are the costs of converting/porting our current code base? Changed line 47 from:
- Parallelization: allow use of other MPI frameworks (\ to:
- Parallelization et al.: allow use of other MPI frameworks (\ Changed line 49 from:
OpenMPI) and improved usage to:
OpenMPI), improved usage Changed lines 52-53 from:
MPI + OpenMP). to:
MPI + OpenMP) and NetworkSpaces with Sleigh (note that the later can be used with both Python and R). Changed line 62 from:
- Pre-canned binnaries (e.g., Debian, Ubuntu, RH). to:
- Pre-canned binnaries (e.g., Debian, Ubuntu, FC). June 05, 2006, at 09:36 AM
by -
Added lines 1-65:
AsteriasDevelopmentPageAsterias would gladly accept new developers and contributors. Short and midtermThe following is an incomplete list of features/additions where people could immediately contribute: - SignS: a couple of new methods, and speeding up the threshold gradient\ descent code. Use C/C++ and improve parallelization. - In most R code (specially SignS and ADaCGH): parallelize figure creation. - All calls from CGI to the rest of the code: how to allow use of job schedulers (e.g., SGE)? - Virtualization: would allow easier testing, increased security and download of pre-canned "distributions" for both real multinode and single node cluster; Linux VServer and/or Xen look like appropraite candidates with low overhead. - Security: all of Asterias. Throughly test and poke Asterias for security holes and provide patches. Open design and achitecture issues- Python Content Management Systems and Application Frameworks. What would we gain from using frameworks such as Webware, CherryPy, or Karrigell? What about portability? - Alternatives to having a server per node? What do we gain from having a (pair of) centralized web server node which distributes jobs to other nodes? Longer term- Parallelization: allow use of other MPI frameworks (MPICH, OpenMPI) and improved usage of clusters of SMP machines (Unified Parallel C, MPI + OpenMP). - Grid: make Asterias capable of using grids. - Result annotation via a notebook-like interface that allows for distributed editing. - Turn into web services. - Pre-canned binnaries (e.g., Debian, Ubuntu, RH). |