<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>Hi Daniel,</div>
<div><br>
</div>
<div>Glad to hear the docs have been useful to you!</div>
<div><br>
</div>
<div>Right now, our configuration scheme isn't well-suited to irregularity - annotations help delineate "sections" of LPs, but not if you want to "pick and choose" LPs. I would suggest a separate configuration routine for this. One option for your case is to
have a whitelist of torus nodes to run that you check at runtime, set up via an LP "configure" function you call in main. You could either have a file with a set of IDs (relative IDs would be good here, that you would translate via codes_mapping_lpid_from_relative),
or if you want a "topology-aware" mapping, a set of torus coordinates (there's utilities for torus mapping functions in codes-net/codes/model-net-inspect.h).</div>
<div><br>
</div>
<div>Hope this helps!</div>
<div>John</div>
<div><br>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span><<a href="mailto:codes-ross-users-bounces@lists.mcs.anl.gov">codes-ross-users-bounces@lists.mcs.anl.gov</a>> on behalf of Daniel Parker <<a href="mailto:dkparker@uchicago.edu">dkparker@uchicago.edu</a>><br>
<span style="font-weight:bold">Date: </span>Monday, July 6, 2015 at 3:31 PM<br>
<span style="font-weight:bold">To: </span>"<a href="mailto:codes-ross-users@lists.mcs.anl.gov">codes-ross-users@lists.mcs.anl.gov</a>" <<a href="mailto:codes-ross-users@lists.mcs.anl.gov">codes-ross-users@lists.mcs.anl.gov</a>><br>
<span style="font-weight:bold">Subject: </span>[codes-ross-users] Workarounds to allow idle nodes in Torus Network?<br>
</div>
<div><br>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>
<div>
<div dir="ltr">
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>Hello,<br>
<br>
</div>
My name is Daniel Parker, and I'm an undergrad in the BigDataX REU, in which I am doing benchmarking on 3D torus networks using CODES/ROSS. I am interested in studying latency and throughput over the network as the number of nodes in communication increases,
from just one pair of nodes to a fully busy network. However, I noticed in the MN_TODO file (/codes-net/src/models/networks/model-net) that idle nodes within the torus network have not yet been implemented. Indeed, when I attempt to have less repetitions of
my servers than the total number of nodes in the network, the simulation will not run (as expected).<br>
<br>
</div>
I am wondering whether in the mean time there is any way that I can achieve this sort of functionality. One idea that I had was to use annotations to specify some nodes as having "dummy" kickoff handlers that do not give them work. However, my concern is that
use of annotations could introduce a systematic nature to the "off" nodes, i.e. having them all have the same x coordinate or be close together or something of that sort, whereas I would want them to be randomly distributed across the network. This concern
comes from uncertainty as to how codes-net constructs the network in such heterogeneous models.<br>
<br>
</div>
So my question is whether there is a way to achieve these sorts of randomly distributed idle nodes within a torus network, so as to model some-to-some communication. Can annotations do what I want? Or is there some other work-around as of now?<br>
<br>
</div>
Thank you for your time. I appreciate the work that has gone into CODES and ROSS, especially the well-commented example files and the GETTING_STARTED files, which have proved very useful.<br>
<br>
</div>
Best,<br>
<br>
</div>
Daniel Parker<br>
</div>
Computer Science<br>
</div>
University of Chicago 2017<br>
</div>
</div>
</div>
</blockquote>
</span>
</body>
</html>