You can use HTCondor to run the nextnano software on your local computer infrastructure (“on-premise”). Essentially, the nextnanomat software submits the job either locally or on the “HTCondor” cluster.
This feature is only supported with our new license system.
Download recommended HTCondor installer from HTCondor.
Download and download
Current Stable Release (e.g. HTCondor 8.6.12) from
We recommend the Native Package for Windows.
File. (Click to download). When you download you have to enter your name, email address and institution.
Nextand accept License Agreement
Create a new HTCondor Pooland fill in the name of the Pool, e.g.
nextnanoCondorPool. This is a unique name for your pool of machines.
Join an existing HTCondor Pooland fill in the hostname of the central manager, e.g. computername where
nextnanoCondorPoolhas been created.
Submit jobs to HTCondorPooland choose
Always run jobs and never suspend them.(Alternative: If you do not want other people to run jobs on your machine at all, select
Do not run jobs on this machineor if you do not want other people to run jobs on your machine while you are working, select
When keyboard has been idle for 15 minutes.. You can of course modify these settings later.)
www).) All PCs of your network should get the same domain name, this does not necessarily be your Windows domain.
$(CONDOR_HOST), $(IP_ADDRESS), *.yourdomainname.com, 192.168.178.*, (Replace *.cs.wisc.edu with your domain name and add your local IP subnet e.g. 192.168.178.*)
On Windows you can obtain your IP subnet using cmd.exe with the ipconfig command.
Program files seem to be problematic, so we do not recommend to use that directory
Install(You need Administrator rights.)
condor_store_cred add -debugfor more output information on the error.
Hostname (for HTCondor pool): computername.yourcompanyname.com Policy: "Always run jobs" Accounting domain: yourcompanyname.com Read access: * Write access: $(CONDOR_HOST), $(IP_ADDRESS), *.yourcompanyname.com Administrator: $(IP_ADDRESS)
You can find your condor config settings in the file
Let's look at an example.
RELEASE_DIR = C:\condor LOCAL_CONFIG_FILE = $(LOCAL_DIR)\condor_config.local REQUIRE_LOCAL_CONFIG_FILE = FALSE LOCAL_CONFIG_DIR = $(LOCAL_DIR)\config use SECURITY : HOST_BASED #CONDOR_HOST: $(FULL_HOSTNAME) # on computer called homer CONDOR_HOST: homer # on computer called lisa COLLECTOR_NAME = TheSimpsonsCondorPool # only on computer called homer #UID_DOMAIN = # empty if you do not have a domain UID_DOMAIN = simpson.com SOFT_UID_DOMAIN=TRUE # entry is missing if you do not have a domain FILESYSTEM_DOMAIN = simpson.com # entry is missing if you do not have a domain CONDOR_ADMIN = SMTP_SERVER = ALLOW_READ = * ALLOW_WRITE = $(CONDOR_HOST), $(IP_ADDRESS), *.simpson.com, 192.168.188.*, 2001:db8:2042::* ALLOW_ADMINISTRATOR = $(IP_ADDRESS) use POLICY : ALWAYS_RUN_JOBS #use POLICY : DESKTOP WANT_VACATE = FALSE WANT_SUSPEND = TRUE #DAEMON_LIST = MASTER SCHEDD COLLECTOR NEGOTIATOR STARTD # on computer called homer DAEMON_LIST = MASTER SCHEDD STARTD # on computer called lisa
condor_submit <filename>.subSubmit a job to the pool.
condor_qShows current state of own jobs in the queue.
condor_q -nobatch -global -allusersShows state of all jobs in the cluster. Of all users.
condor_q -goodput -global -allusersShows state and occupied CPU of all jobs in the cluster.
condor_q -allusers -global -analyzeDetailed information for every job in the cluster.
condor_q -global -allusers -holdShows why jobs are in hold state.
condor_statusShows state of all available resources.
condor_rmRemove jobs from a queue:
condor_rm -allRemoves all jobs from a queue.
condor_rm <cluster>.<id>Removes jobs on cluster <cluster> with id <id> (It seems
<cluster>.can be omitted, and
condor_release -allIf any jobs are in state hold, use this command to restart them.
condor_restartRestart all condor daemons/services after changes in config file.
condor_versionReturns the version number of HTCondor
condor_store_cred queryReturns info about the credentials stored for HTCondor jobs
Q: I submitted a job to HTCondor, but the Batch line of nextnanomat is stuck with
preparing. What is wrong?
A1: Did you store your credentials after the installation of HTCondor? If not, enter
condor_store_cred add into the command prompt to add your password, see above (Recommended Installation Process).
A2: Did you change your password recently? If yes you have to reenter your credentials for HTCondor.
condor_store_cred add into the command prompt to add your password, see above (Recommended Installation Process). If this does not work, try to enter
condor_store_cred add -debug for more output information on the error.
Q: I specified target machines in Tools - Options. Afterwards every submitted job to HTCondor is stuck with
transmitting. What is wrong?
A: The value for
UID_DOMAIN within the condor_config file needs to be the same for every computer of your cluster. (You can easily test it in a command prompt with
condor_status -af uiddomain) If it's not the same value, no matching computer will be found and the job won't be transmitted successfully.
If you receive the following error when you type in
C:\Users\"<your user name>">condor_status Error: communication error CEDAR:6001:Failed to connect to <123.456.789.123>
you can check whether the computer associated with this IP address is your HTCondor computer using the following command.
If it is not the expected computer, you can open a Command Prompt as Administrator and type in
ipconfig /flushdns to flush the DNS Resolver Cache.
C:\Users\"<your user name>">ipconfig /flushdns
(We are working on it.)