Hi Samuel, re: > Any luck on this one? I am assuming you are referring to the question that follows. If not, please let me know what this is in reference to. > Also, I've noticed that our dmbin.k has been eating up > lots of CPU time. It's at around 25%, which is abnormal for our machine. > I've > added some CONDUIT, and NIMAGE data, but I didn't think it would affect > dmbin.k > that much. The easiest way to determine if the addition of CONDUIT data has caused an increase in DMBIN (dmbin.k) processing (NIMAGE is imagery, not grids so it will not affect DMBIN) is to comment out the additions you made and see if the load comes down. Cheers, Tom **************************************************************************** Unidata User Support UCAR Unidata Program (303) 497-8642 P.O. Box 3000 address@hidden Boulder, CO 80307 ---------------------------------------------------------------------------- Unidata HomePage http://www.unidata.ucar.edu **************************************************************************** Ticket Details =================== Ticket ID: XRR-599672 Department: Support McIDAS Priority: Normal Status: Closed
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.