Open GoogleCodeExporter opened 9 years ago
Federica - can you please try these steps and let me know how it goes?
(1) Right-click on the failed red Data-sink of the results and select Restart
Module? This should try to relink/provision the results into the specified
location in the data sink.
(2) Right-click on the data-sink and select "Show Errors" what does it show?
(3) Please confirm that there are no permission restrictions on
writing/overwriting the results in the data-sink.
This workflow is run on fgene3 (which is also patched, Bernard emailed me), but
I have no account and can;t see the state/results locations.
- Ivo
Original comment by iwaterp...@gmail.com
on 20 Jul 2011 at 11:08
Federica - can you please try these steps and let me know how it goes? FT: My
replie s r into the message.
(1) Right-click on the failed red Data-sink of the results and select Restart
Module? This should try to relink/provision the results into the specified
location in the data sink.
Done, it fails again.
(2) Right-click on the data-sink and select "Show Errors" what does it show?
See picture, nothing, blank.
(3) Please confirm that there are no permission restrictions on
writing/overwriting the results in the data-sink.
No eprmissions: drwxrwxrwx 2 ftorri genetics 4096 Jul 19 16:14
PERM_SE_results
This workflow is run on fgene3 (which is also patched, Bernard emailed me), but
I have no account and can;t see the state/results locations.
FT: do u wanna me to try also on fgene1? Ia am using fgene3 to let fgene1 to
andy not exhausting the fgene1 capabilities.
- Ivo
Original comment by federica...@gmail.com
on 20 Jul 2011 at 11:24
Attachments:
Yes, could you please run the workflow on fgene1 as well and also double check
the entire PATH of the output files (e.g., to ensure that you can write in each
folder from the root / up to the leaf filename.
Original comment by iwaterp...@gmail.com
on 20 Jul 2011 at 11:32
Ok, doing it.
fed
Original comment by federica...@gmail.com
on 20 Jul 2011 at 11:58
On fgene1 it worked well as I wrote you in the email.
fed
Original comment by federica...@gmail.com
on 21 Jul 2011 at 9:44
Original issue reported on code.google.com by
federica...@gmail.com
on 20 Jul 2011 at 6:56Attachments: