Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handle replication of data in TIMESERIES #149

Open
pausz opened this issue Feb 5, 2018 · 0 comments
Open

Handle replication of data in TIMESERIES #149

pausz opened this issue Feb 5, 2018 · 0 comments

Comments

@pausz
Copy link
Contributor

pausz commented Feb 5, 2018

From @stuart-knock

The replication of timeseries to a vector length nodes for Q is
redundant when there is no explicit space to them. A single number
would be all that needs to be returned with mapping to nodes done
in Timeseries::fire(). The exception is for noise, where we want a
different random sequence at each point in space and typically it is applied to all nodes anyway. Sometimes the noise is applied on the border of the spatial domain to study wave fronts.

To maintain a consistent interface,
it is probably best to have the vector returned by the individual
TIMESERIES fire() methods be of length the number of nodes that the
stimulus will be applied to... Resolving this issue becomes more important for higher
resolutions of the spatial domain, where currently applying a stimulus to a single
node of a 1000x1000 grid will produce a million element vector,
rather than the single number that is required...

Add vector of indices with the subset of indices that receives stimuli ... Mmmm that sounds familiar ...
Oh, yes, there is some other very nice piece of software that has a general way to do that 😛 ...

@pausz pausz added the optimize label Feb 5, 2018
@pausz pausz added this to In progress in NFTsim power-ups Feb 5, 2018
@stuart-knock stuart-knock added this to the TBD 1 milestone Feb 9, 2018
@stuart-knock stuart-knock moved this from In progress to To Do in NFTsim power-ups Feb 9, 2018
@stuart-knock stuart-knock removed their assignment Sep 11, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Development

No branches or pull requests

2 participants