New package: SpikeNetOpt v0.1.0

[JuliaRegistrator]

• Registering package: SpikeNetOpt
• Repository: https://github.com/russelljjarvis/SpikeNetOpt.jl
• Created by: @russelljjarvis
• Version: v0.1.0
• Commit: 2dfd4a9d0cbd532b77d5c693fed5c0f16b3d287b
• Reviewed by: @russelljjarvis
• Reference: @JuliaRegistrator register russelljjarvis/SpikingNeuralNetworks_.jl#18 (comment)
• Description: Julia has enough tools to support fitting spiking neural network models to data. Python speed necessitates external simulators to do network simulation. As much as possible it would be nice to do fast, efficient data fitting of spike trains to network models in one language, lets try to do that here.

[github-actions]

Your new package pull request does not meet the guidelines for auto-merging. Please make sure that you have read the General registry README and the AutoMerge guidelines. The following guidelines were not met:

• The following dependencies do not have a [compat] entry that is upper-bounded and only includes a finite number of breaking releases: Conda, DataStructures, Distributions, Evolutionary, JLD, LightGraphs, Metaheuristics, OrderedCollections, Parameters, PyCall, SpikeSynchrony, SpikingNeuralNetworks, UnPack, UnicodePlots
• I was not able to install the package (i.e. Pkg.add("SpikeNetOpt") failed). See the CI logs for details.
• I was not able to load the package (i.e. import SpikeNetOpt failed). See the CI logs for details.

Note that the guidelines are only required for the pull request to be merged automatically. However, it is strongly recommended to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human.

After you have fixed the AutoMerge issues, simple retrigger Registrator, which will automatically update this pull request. You do not need to change the version number in your Project.toml file (unless of course the AutoMerge issue is that you skipped a version number, in which case you should change the version number).

If you do not want to fix the AutoMerge issues, please post a comment explaining why you would like this pull request to be manually merged.

Since you are registering a new package, please make sure that you have also read the package naming guidelines: https://julialang.github.io/Pkg.jl/dev/creating-packages/#Package-naming-guidelines-1

---

If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.

[giordano]

@russelljjarvis please see the message above. Once you fix the automerge issues you can register again the new revision without changing the version number and this pull request will be automatically updated.

[noblock]

[russelljjarvis]

Hi @giordano, sorry yes. I have been abusing the Julia Register bot (I have been using its messages to try to debug package conflicts). I have been having a lot grief with package conflicts, that didn't exist when I installed modules and developed code, but do exist when I try to re-install my code as a Julia package.

In the meantime, I think I have fixed all of the package conflicts, so I will try one more time. Sorry again, I didn't mean to escalate a problem up to the level of human interaction.

[github-actions]

This pull request has been inactive for 30 days and will be automatically closed 7 days from now. If this pull request should not be closed, please either (1) fix the AutoMerge issues and re-trigger Registrator, which will automatically update the pull request, or (2) post a comment explaining why you would like this pull request to be manually merged. [noblock]

[russelljjarvis]

It's fine to close for now, under the assumption fix problems and try to make package later I think.