Re: [Ifeffit] ERROR in getting feff8 input file for YBCO from Web atoms
Feng, Matt, The problem appears to be caused by a error in parsing the Titles portion of this one particular ATOMS.INP file. If you delete the entire reference #2 in the titles area WEBAtoms runs fine. (refer2: Cava, et al, Physica C 165, p.419, (1990)). Error can be reproduced by: 1) Choose YBa2Cu3O7.inp : yttrium barium copper oxide ( 123 , ybco) entry in http://cars9.uchicago.edu/cgi-bin/atoms/Atoms-Search.cgi and run WebAtoms 2) Choose K-edge 3) Run ATOMS (You will see the ERROR ACCESS Denied) The work around: 1) Choose YBa2Cu3O7.inp : yttrium barium copper oxide ( 123 , ybco) entry in http://cars9.uchicago.edu/cgi-bin/atoms/Atoms-Search.cgi and run WebAtoms 2) Choose K-edge 3) Delete (refer2: Cava, et al, Physica C 165, p.419, (1990)) in the header. 4) Run ATOMS (and it now works fine). Dave
-----Original Message----- From: ifeffit-bounces@millenia.cars.aps.anl.gov [mailto:ifeffit-bounces@millenia.cars.aps.anl.gov] On Behalf Of Feng Wang Sent: Wednesday, February 07, 2007 2:01 AM To: XAFS Analysis using Ifeffit Subject: Re: [Ifeffit] ERROR in getting feff8 input file for YBCO from Webatoms
Thank you, Paul, for clarifying this problem.
Sincerely,
Feng
Just to follow on this -- I can access the YBCO atoms entry (via a search). The atoms.inp pops up correctly, but when I attempted to run atoms, I got the same error message. The error doesn't come from my end (as far as I can tell). The problem seems to be with the execution of atoms (e.g. hitting the button "Run atoms".). The cgi is probably broken.
Paul
ERROR
Access Denied
Access Denied by security policy The security policy for your network prevents your request from being allowed at this time. Please contact your administrator if you feel this is incorrect.
On Feb 3, 2007, at 2:42 AM, Matt Newville wrote:
Hi Feng,
Sorry for the trouble. I'm not sure where the problem is. I can get files from the Atoms archive from home (ie, outside the Argonne network), and I don't see any recent errors in the logs, suggesting that both the server connections and the access through the Argonne and APS firewalls are working. Could it be that the trouble is at your end?
Perhaps we can troubleshoot this a little better. Does the 'search for Atoms.inp' page http://cars9.uchicago.edu/~newville/adb/search.html appear for you? Is it responsive?
Can you select a central atoms, a structure, and then hit 'Run Webatoms'?
Can you browse to http://cars9.uchicago.edu/atomsdb/ and see a large number of atoms.inp files? Can you select and download some of these files?
Hope that helps,
--Matt _______________________________________________ Ifeffit mailing list Ifeffit@millenia.cars.aps.anl.gov http://millenia.cars.aps.anl.gov/mailman/listinfo/ifeffit
_______________________________________________ Ifeffit mailing list Ifeffit@millenia.cars.aps.anl.gov http://millenia.cars.aps.anl.gov/mailman/listinfo/ifeffit
==================================== EM group Physics & NINT Phone: (780)6411667 http://www.phys.ualberta.ca/~fwang _______________________________________________ Ifeffit mailing list Ifeffit@millenia.cars.aps.anl.gov http://millenia.cars.aps.anl.gov/mailman/listinfo/ifeffit
On Wednesday 07 February 2007 05:36, Barton, David (DG) wrote:
The problem appears to be caused by a error in parsing the Titles portion of this one particular ATOMS.INP file. If you delete the entire reference #2 in the titles area WEBAtoms runs fine. (refer2: Cava, et al, Physica C 165, p.419, (1990)).
Error can be reproduced by: 1) Choose YBa2Cu3O7.inp : yttrium barium copper oxide ( 123 , ybco) entry in http://cars9.uchicago.edu/cgi-bin/atoms/Atoms-Search.cgi and run WebAtoms 2) Choose K-edge 3) Run ATOMS (You will see the ERROR ACCESS Denied)
The work around: 1) Choose YBa2Cu3O7.inp : yttrium barium copper oxide ( 123 , ybco) entry in http://cars9.uchicago.edu/cgi-bin/atoms/Atoms-Search.cgi and run WebAtoms 2) Choose K-edge 3) Delete (refer2: Cava, et al, Physica C 165, p.419, (1990)) in the header. 4) Run ATOMS (and it now works fine).
Dave, That is an AMAZING piece of detective work. I am floored that you figured out something so weird and specific. Great job! I will try to find some time this week to figure out the underlying cause of the problem and update webatoms. B -- Bruce Ravel ---------------------------------------------- bravel@anl.gov Molecular Environmental Science Group, Building 203, Room E-165 MRCAT, Sector 10, Advanced Photon Source, Building 433, Room B007 Argonne National Laboratory phone and voice mail: (1) 630 252 5033 Argonne IL 60439, USA fax: (1) 630 252 9793 My homepage: http://cars9.uchicago.edu/~ravel EXAFS software: http://cars9.uchicago.edu/~ravel/software/exafs/
Feng, Paul, Dave,Bruce, Thanks for the reports. I can reproduce this problem, and I'm pretty sure it's not exactly a problem with the cgi script, but more of an APS/ANL firewall issue. That is, inside the APS firewall, I can run webatoms on this file (unmodified) and get the correct result. It's not simply an issue with 'refer2', because even outside the firewall, I can get other files with a 'refer2' tag in them (try ZnOH2.inp, for example). In addition, leaving the 'refer2' in, and taking the 'refer1' line out also generates a correct output. Also: even outside the firewall, I can get http://cars9.uchicago.edu/atomsdb/YBa2Cu3O7.inp In addition, generating the feff.inp file, and copying this file to http://cars9.uchicago.edu/atomsdb/ybco_feff1.inp I can access that file as well (which might help Feng) So, it appears that the firewall is not simply blocking files that contain the string: refer2: Cava, et al, Physica C 165, p.419, (1990) but does appear to be blocking URLs that contain certain strings (or perhaps strings of a certain length??). I would guess that changing the cgi script to use POST instead of GET would be the simplest way to solve this problem. --Matt
I must admit that at least inside of the ANL lan, I was very (un) impressed with the firewall and the questionable judgments it made based upon content for access of material from outside ANL. I never suspected that it would try a filter scheme for things inside ANL. Bizarre. On Feb 8, 2007, at 4:14 AM, Matt Newville wrote:
Feng, Paul, Dave,Bruce,
Thanks for the reports. I can reproduce this problem, and I'm pretty sure it's not exactly a problem with the cgi script, but more of an APS/ANL firewall issue. That is, inside the APS firewall, I can run webatoms on this file (unmodified) and get the correct result.
It's not simply an issue with 'refer2', because even outside the firewall, I can get other files with a 'refer2' tag in them (try ZnOH2.inp, for example). In addition, leaving the 'refer2' in, and taking the 'refer1' line out also generates a correct output.
Also: even outside the firewall, I can get http://cars9.uchicago.edu/atomsdb/YBa2Cu3O7.inp In addition, generating the feff.inp file, and copying this file to http://cars9.uchicago.edu/atomsdb/ybco_feff1.inp I can access that file as well (which might help Feng)
So, it appears that the firewall is not simply blocking files that contain the string: refer2: Cava, et al, Physica C 165, p.419, (1990) but does appear to be blocking URLs that contain certain strings (or perhaps strings of a certain length??).
I would guess that changing the cgi script to use POST instead of GET would be the simplest way to solve this problem.
--Matt _______________________________________________ Ifeffit mailing list Ifeffit@millenia.cars.aps.anl.gov http://millenia.cars.aps.anl.gov/mailman/listinfo/ifeffit
participants (4)
-
Barton, David (DG) -
Bruce Ravel -
Matt Newville -
Paul Fons