##// END OF EJS Templates
update SGEEngineSet to use SGE job arrays...
update SGEEngineSet to use SGE job arrays SGE job arrays allow one job id to be associated with a set of processes on an SGE cluster. modified SGEEngineSet to be a subclass PBSEngineSet ipcluster will now generate a default SGE job script if --sge-script is not provided. most folks should ignore the --sge-script option unless they know they need it. if --sge-script is passed, check that the script exists and that the user has defined a "#$ -t" setting within the script. if not, add the setting for them by copying the script to a temp file and launching the job array using the modified temp file. ipengines terminate cleanly now when the ipcluster command exits. i think we still need to handle furl files when engines are assigned to different hosts via SGE. without using ssh or nfs, the only other way is to put the contents of the furl in the job script before submission but this is less secure. need to discuss this.

File last commit:

r1250:f658828f
r2675:225cd966
Show More
COPYING.txt
76 lines | 3.4 KiB | text/plain | TextLexer
IPython is licensed under the terms of the new or revised BSD license, as follows:
Copyright (c) 2008, IPython Development Team
All rights reserved.
Redistribution and use in source and binary forms, with or without modification,
are permitted provided that the following conditions are met:
Redistributions of source code must retain the above copyright notice, this list of
conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list
of conditions and the following disclaimer in the documentation and/or other
materials provided with the distribution.
Neither the name of the IPython Development Team nor the names of its contributors
may be used to endorse or promote products derived from this software without
specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
About the IPython Development Team
----------------------------------
Fernando Perez began IPython in 2001 based on code from Janko Hauser <jhauser@zscout.de>
and Nathaniel Gray <n8gray@caltech.edu>. Fernando is still the project lead.
The IPython Development Team is the set of all contributors to the IPython project.
This includes all of the IPython subprojects. Here is a list of the currently active contributors:
* Matthieu Brucher
* Ondrej Certik
* Laurent Dufrechou
* Robert Kern
* Brian E. Granger
* Fernando Perez (project leader)
* Benjamin Ragan-Kelley
* Ville M. Vainio
* Gael Varoququx
* Stefan van der Walt
* Tech-X Corporation
* Barry Wark
If your name is missing, please add it.
Our Copyright Policy
--------------------
IPython uses a shared copyright model. Each contributor maintains copyright over
their contributions to IPython. But, it is important to note that these
contributions are typically only changes to the repositories. Thus, the IPython
source code, in its entirety is not the copyright of any single person or
institution. Instead, it is the collective copyright of the entire IPython
Development Team. If individual contributors want to maintain a record of what
changes/contributions they have specific copyright on, they should indicate their
copyright in the commit message of the change, when they commit the change to
one of the IPython repositories.
With this in mind, the following banner should be used in any source code file to
indicate the copyright and license terms:
#-------------------------------------------------------------------------------
# Copyright (C) 2008 The IPython Development Team
#
# Distributed under the terms of the BSD License. The full license is in
# the file COPYING, distributed as part of this software.
#-------------------------------------------------------------------------------