Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
K
kwant
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Anton Akhmerov
kwant
Commits
37981f62
Commit
37981f62
authored
10 years ago
by
Christoph Groth
Browse files
Options
Downloads
Patches
Plain Diff
to-do entries
parent
708d1a3e
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
TODO
+15
-2
15 additions, 2 deletions
TODO
with
15 additions
and
2 deletions
TODO
+
15
−
2
View file @
37981f62
...
...
@@ -57,6 +57,10 @@ Roughly in order of importance. -*-org-*-
there exists an object of the same name in Kwant. (Consider the usage of
linking for the term "Thread" in the document linked above.)
* Harmonize numerical tolerances throughout Kwant
By default, a channel should open at the same energy in any solver.
If this is possible, we may want to have one central tolerance setting.
* Plotter: show site upon click
* fix physics.noise (docstring, __all__, etc.)
...
...
@@ -134,8 +138,17 @@ Roughly in order of importance. -*-org-*-
* Ideas for kwant 2
** Consider whether to use *args or args in System.hamiltonian
** Names to be reconsidered
- lead_info
** lead_info
Currently, lead_info is either of two things, a sequence of propagating modes or a sequence of self-energies.
- There is no need to have lead_info as an attribute of BlockResult.
- In the case of SMatrix and GreensFunction this attribute should be renamed to what it is, i.e. propagating_modes and selfenergies.
- In cases where a common name is needed (i.e. return value of _make_linear_sys), a better name might be lead_data or solved_leads.
- BlockResult itself could be renamed to something more specific, perhaps GeneralSMatrix.
** Unify the order of indices
For example in wave_function and in PropagatingModes.
** Take advantage of when a system is known to be Hermitian
Either
- omit the lead with most open channels by default when calling smatrix and greens_function or
- verify that the scattering matrix is indeed current-conserving (it might be not due to numerical error)
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment