Add function to inform callers on optimum number of file parts

It would be nice if Silo could portably determine the optimum number of file parts for a given dump. The idea is that for a given MPI communicator, there is probably set number of I/O nodes the caller can actually see. Using more parts than than some multiple (maybe 1) of that number may not be too useful.

-----------------------REDMINE MIGRATION-----------------------
This ticket was migrated from Redmine. As such, not all
information was able to be captured in the transition. Below is
a complete record of the original redmine ticket.

Ticket number: 1877
Status: New
Project: VisIt
Tracker: Feature
Priority: Normal
Subject: Add function to inform callers on optimum number of file parts
Assigned to: -
Category: -
Target version: -
Author: Mark Miller
Start: 06/17/2014
Due date:
% Done: 0%
Estimated time:
Created: 06/17/2014 03:04 pm
Updated:
Likelihood:
Severity:
Found in version:
Impact: 3 - Medium
Expected Use: 3 - Occasional
OS: All
Support Group: Any
Description:
It would be nice if Silo could portably determine the optimum number of file parts for a given dump. The idea is that for a given MPI communicator, there is probably set number of I/O nodes the caller can actually see. Using more parts than than some multiple (maybe 1) of that number may not be too useful.

Comments:

The ticket names no source file, entry point, or test. Start by locating Silo's dump and file-part handling, then examine how a given MPI communicator could determine visible I/O nodes; done means callers can receive a portable optimum file-part count.