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

[MAINT][WIP] Simulate dipole enh #315

Closed

Conversation

jasmainak
Copy link
Collaborator

Just opening the PR with the intent of finishing it later

@jasmainak jasmainak force-pushed the simulate_dipole_enh branch from 9d4b369 to 8356885 Compare April 8, 2021 05:12
@jasmainak
Copy link
Collaborator Author

I could use a bit of help in this @rythorpe or #314

@rythorpe
Copy link
Contributor

What's the goal of this PR besides to add tstop and dt?

While we're at it, wdyt of implementing the capability of a burn-in period?

@jasmainak
Copy link
Collaborator Author

Burn-in would be a bit more complicated I suppose? You'd need to make sure that downstream analysis pipelines are aware of what the burn-in is and adjust the plots accordingly

@jasmainak
Copy link
Collaborator Author

@rythorpe the goal is to get rid of code like this:

params.update({
'tstop': 310.0,
})

as much as possible

@jasmainak jasmainak force-pushed the simulate_dipole_enh branch from 8356885 to 1f881cd Compare June 4, 2021 14:59
@jasmainak
Copy link
Collaborator Author

@cjayb would it be acceptable to you if we made tstop compulsory argument to add_xxx_drives ? Currently, we were secretly passing tstop to Network instead of simulate_dipole which seems a bit semantically wrong to me. I think we might be able to make it more intelligent down the line but it's too tangled for me right now to make any sense of things unless I make it compulsory

@cjayb
Copy link
Collaborator

cjayb commented Jun 5, 2021

which seems a bit semantically wrong to me

Agreed! tstop is a parameter of the simulation, not the network. Poisson and bursty drives already take tstop, but the implementation there is still dependent on the idea that the end-time of a simulation is known at the time the add_XXX-method is called. I don't think this needs to be so. We can do validation/sanity checks on the drive parameters after simulate is called. I think tstop=None still makes sense as a good default for Poisson and bursty, no?

@jasmainak
Copy link
Collaborator Author

closed by #397

@jasmainak jasmainak closed this Jul 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants