Creating a custom tool to submit Condor jobs is fairly common,
especially with a limited domain focus or is heavily site-specific - a
tool to submit ray tracing jobs or EDA simulations, for example. It
seems that there are more web-interfaces than traditional desktop
apps.
A general-purpose Condor GUI, for all sites and all job types,
probably wouldn't be all that helpful. If you can describe a bit more
how you see your
interface working, people who have developed something similar might
be able to volunteer their implementation as a starting point.
On Tue, Aug 5, 2008 at 4:23 PM, Ryan Lewis <me@xxxxxxxxxxxxx> wrote:
Is there anything in particular you'd like to have automated,
or made easier that a GUI might deliver vs. Emacs/vi/Notepad?
The reason why I want it is for researchers I support who don't want
learn how to use Condor, they just want to get there research done.
Alternatively they may want to "learn by doing" such a tool would let
them do that without having to open up a manual.
Creating a custom tool to submit Condor jobs is fairly common,
especially with a limited domain focus or is heavily site-specific - a
tool to submit ray tracing jobs or EDA simulations, for example. It
seems that there are more web-interfaces than traditional desktop
apps.
A general-purpose Condor GUI, for all sites and all job types,
probably wouldn't be all that helpful. If you can describe a bit more
how you see your
interface working, people who have developed something similar might
be able to volunteer their implementation as a starting point.
-Erik
_______________________________________________
Condor-users mailing list
To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx
with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/condor-users
The archives can be found at:
https://lists.cs.wisc.edu/archive/condor-users/