#15 max_io can't be changed in DNAnalysis

[Ferdinando Randisi]

max_io, the argument that encodes the maximum amount of data that can be created per second, cannot currently be edited in DNAnalysis. This seems to be because DNAnalysis does not read it from the input file itself and does not call the method SimBackend::get_settings, that would read it from the input file.

A solution would simply be to copy line 275-279 of SimBackend.cpp (below) somewhere into AnalysisBackend::get_settings

"
// set the max IO
if (getInputNumber<number> (&inp, "max_io", &_max_io, 0) == KEY_FOUND) {
if (_max_io < 0) throw oxDNAException ("Cannot run with a negative I/O limit. Set the max_io key to something > 0");
else OX_LOG(Logger::LOG_INFO, "Setting the maximum IO limit to %g MB/s", _max_io);
}
"</number>

I'm not doing it myself since I'm not entirely sure of how Analysis backend works and I don't want to mess stuff up.

[Flavio]

I propose to disable max_io for DNAAnalysis... Does everyone agree?

[Ferdinando Randisi]

Personally I would set it to something very high: what if I'm being stupid
and writing the mutual distances of 5000 particles in a long trajectory
file?

Setting something like 500MB/s would prevent me from flooding my hard drive.

2015-07-06 18:03 GMT+01:00 Flavio flavioromano@users.sf.net:

I propose to disable max_io for DNAAnalysis... Does everyone agree?

• [tickets:#15] http://sourceforge.net/p/oxdna/tickets/15 max_io can't
  be changed in DNAnalysis*

Status: open
Milestone: 2.0
Created: Mon Jul 06, 2015 04:41 PM UTC by Ferdinando Randisi
Last Updated: Mon Jul 06, 2015 04:41 PM UTC
Owner: nobody

max_io, the argument that encodes the maximum amount of data that can be
created per second, cannot currently be edited in DNAnalysis. This seems to
be because DNAnalysis does not read it from the input file itself and does
not call the method SimBackend::get_settings, that would read it from the
input file.

A solution would simply be to copy line 275-279 of SimBackend.cpp (below)
somewhere into AnalysisBackend::get_settings

"
// set the max IO
if (getInputNumber<number> (&inp, "max_io", &_max_io, 0) == KEY_FOUND) {
if (_max_io < 0) throw oxDNAException ("Cannot run with a negative I/O
limit. Set the max_io key to something > 0");
else OX_LOG(Logger::LOG_INFO, "Setting the maximum IO limit to %g MB/s",
_max_io);
}
"</number>

I'm not doing it myself since I'm not entirely sure of how Analysis
backend works and I don't want to mess stuff up.

---

Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/oxdna/tickets/15/

To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/

--
Ferdinando Randisi

[Lorenzo Rovigatti]

I agree: disabling it altogether is the most sensible fix.

[Petr Sulc]

I agree with disabling as it well.

[Lorenzo Rovigatti]

One could set a very high limit but we would still need a way of overwriting that limit (for obvious reasons). However, I think that it's much more difficult (not to say borderline impossible) to unknowingly fill one's hard drive with DNAnalysis compared to oxDNA, which is why I think that we should just disable the I/O check altogether.

[Ferdinando Randisi]

I really don't mind if we disable it or if we set it to a large value,
since I agree that it's very unlikely to fill the hard drive with
DNAnalysis. Disabling it is fine for me.

2015-07-07 9:31 GMT+01:00 Lorenzo Rovigatti torav@users.sf.net:

One could set a very high limit but we would still need a way of
overwriting that limit (for obvious reasons). However, I think that it's
much more difficult (not to say borderline impossible) to unknowingly fill
one's hard drive with DNAnalysis compared to oxDNA, which is why I think
that we should just disable the I/O check altogether.

---

• [tickets:#15] http://sourceforge.net/p/oxdna/tickets/15 max_io can't
  be changed in DNAnalysis*

Status: open
Milestone: 2.0
Created: Mon Jul 06, 2015 04:41 PM UTC by Ferdinando Randisi
Last Updated: Mon Jul 06, 2015 06:37 PM UTC
Owner: nobody

max_io, the argument that encodes the maximum amount of data that can be
created per second, cannot currently be edited in DNAnalysis. This seems to
be because DNAnalysis does not read it from the input file itself and does
not call the method SimBackend::get_settings, that would read it from the
input file.

A solution would simply be to copy line 275-279 of SimBackend.cpp (below)
somewhere into AnalysisBackend::get_settings

"
// set the max IO
if (getInputNumber<number> (&inp, "max_io", &_max_io, 0) == KEY_FOUND) {
if (_max_io < 0) throw oxDNAException ("Cannot run with a negative I/O
limit. Set the max_io key to something > 0");
else OX_LOG(Logger::LOG_INFO, "Setting the maximum IO limit to %g MB/s",
_max_io);
}
"</number>

I'm not doing it myself since I'm not entirely sure of how Analysis
backend works and I don't want to mess stuff up.

---

Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/oxdna/tickets/15/

To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/

--
Ferdinando Randisi

[Flavio]

This should be fixed now with the latest commits. Closing the ticket for now.