nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Where are the geoprocessing results?

FionaGregory

When I run a geoprocessing tool from ArcCatalog or ArcMap, the messages regarding the progress/success/warnings related to the running of the tool can be found in the Results window.
When I run arcpy geoprocessing tools from a Python script from the Python Shell, where does this report on the results go? Can I get it to print to the screen, or direct it to a file?
Thanks,
Fiona

Encuentra más publicaciones etiquetadas con

Accepted answers

ChrisSnyder

I use

arcpy.GetMessages() #returns all messages (messages, errors, warnings, etc)

Take a look at the documentation: http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#//00150000000p000000.htm

All comments

ChrisSnyder

I use

arcpy.GetMessages() #returns all messages (messages, errors, warnings, etc)

Take a look at the documentation: http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#//00150000000p000000.htm

FionaGregory

This was a good answer.

If I put

print arcpy.GetMessages()

in my script, it will print the messages from the latest tool that was run.
However, of course it will not print these messages until after the tool has run.
In my case, I prefer to see it while because I am having a problem with something hanging.

To see the results WHILE the tool is being run I think I have to convert the script into a script tool so I can run it from ArcCatalog.

ChrisSnyder

I don't think there is a way to return the messages in "real time"... but you could do something like:

print "Attempting to Clip..."
arcpy.Clip_analysis(...)
print "Clip completed..."

try:
   arcpy.Clip_analysis(...)
except:
   print "Clip failed!"

What leads you to believe the tool is hanging vs. just taking a long time?

JoeKoch_0-1775238143111.png

JoeKoch_1-1775238194791.png

FionaGregory

Hi Chris

Seeing the Results in real time is how I can tell if it is hanging or not. If it is "Writing Feature xyz" and #xyz keeps changing, I know it is working. If it gets stuck and the feature # does not change, and the Messages don't change either (it does not proceed to a further stage) I know it is hanging. Thus the need to see the Results.

F.

ChrisSnyder

I don't think you can get a hook into the realtime tool messages. However...

Maybe the feature it appears to be hanging on is just a large feature that requires extra time to process? If you look at this feature (probably has the same OBJECTID field value as the message indicates), is there something unusual about it? How many verticies does it have?

The TaskManger can be a useful tool in diagnosing things like this. While the tool appears to hang, what is going in parent process (ArcMap.exe if you are calling the tool from that application). Is the processor or RAM usage fluctuating? Do you see the read and/or write bytes increasing? How long will the tool run if you don't cancel it?

Also, if the tool is indeed hanging, would your script do something else (like try an alternate tool, or use a modified tool parameter)?

While it may be more complex than you are wanting to do, you could accomlish a sort of "time out" process by using the "subprocess" module.

Brian_McLeer_0-1775242710211.png

icon_youTube.png

Únete a la Conversación

Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.

Enlaces Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.