Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wildcards not accepted in outputfiles for Condor jobs #2014

Open
kh296 opened this issue Feb 22, 2022 · 6 comments
Open

Wildcards not accepted in outputfiles for Condor jobs #2014

kh296 opened this issue Feb 22, 2022 · 6 comments

Comments

@kh296
Copy link
Contributor

kh296 commented Feb 22, 2022

I've tried to include a wildcard when specifying outputfiles, using either:

j.outputfiles = [LocalFile('*.pdf')]

as suggested in the documentation for input and output data or using

j.outputfiles = '*.pdf'

In both cases the job completes successfully on Condor, but then there's a problem with the output retrieval:

error reading from /var/work/condor/execute/dir_171116/*.pdf: (errno 2) No such file or directory;

Am I using the wrong syntax, or is there a problem with wildcards in outputfilenames when running on Condor? If I specify the exact filenames, these are retrieved.

@mesmith75
Copy link
Contributor

mesmith75 commented Feb 23, 2022

Related to #1956

@egede
Copy link
Member

egede commented Mar 29, 2022

Also assigned as good first issue

@abhijeetsharma200
Copy link
Collaborator

Hi,

I am interested in contributing Ganga as part of GSOC'23. I wanted to ask if Ganga is going to be a part of GSoC this year.

Additionally, I am interested in helping with this issue if it is still available. I have cloned the repo using the Installation guide in the docs.

I am unfortunately unable to replicate the issue by following the steps in the documentation for input and output data.

Any help would be greatly appreciated. I am looking forward to contributing in the future.

Abhijeet

@egede
Copy link
Member

egede commented Jan 31, 2023

Hi @abhijeetsharma200 ,

Thanks for getting in contact. We do indeed plan to be part of GSoC 2023.

Regarding the issue here, the problem should only show up if you are using the Condor backend. Was that what you tried? To get access to a Condor bacth system, the best is to install the docker container that gives you a mini test environment. Take a look at how this is done in the continuous integration.

@abhijeetsharma200
Copy link
Collaborator

Hi @egede,

Thank you for your response. I am excited to contribute to Ganga in the coming months and to participate in GSoC 2023.

I followed the GitHub installation instructions from the documentation inside WSL on Ubuntu 22.04 and tried to reproduce the error using the steps above. However, I am now setting up the docker container as you suggested.

I also wanted to inquire if there is an IRC or Slack for Ganga?

@egede
Copy link
Member

egede commented Feb 1, 2023

Communication is an important part of working in GSoC. We use the CERN Mattermost server for instant messaging about the project. Please

  • Create a CERN external account by following the instructions
  • Follow the link to join the Ganga Team in MatterMost. You can install MatterMost as an application, or you can just use it inside your browser.
  • When you have joined the Ganga Team, please join the GSoC2023 channel.
  • Introduce yourself with a few words to the channel.

It is by far the best if most communication is public in the MatterMost channel, but you can also instant message @egede, @masmith and @arichard for more specific issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants