sc arguments should be named cell
See original GitHub issueDescribe the bug
sc
keyword arguments are used in a few places.
All these should be named cell
to make it clear what it is.
The main problem is that sc
has been used since the beginning, so probably we need to have it allowed (until it truly becomes deprecated)
The following should be changed:
- Change
SuperCell
toCell
- Change
sc
arguments tocell
- Allow
sc
arguments via `**kwargs`` for fall-back and backward compatibility
Now I have a problem with the attached supercell instances. E.g. Geometry.sc
(and all the other classes) is now a bit misleading.
How should this object be renamed (HELP WANTED):
obj.abc
for a-b-c lattice vectorsobj.uc
for unit-cellobj.c
for cellobj.cell
, this is the only thing that won’t work becauseobj.cell
already refers to the cell-vectorsobj.*
other suggestions?
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Define and use names in formulas - Microsoft Support
Type the first letter of the name, and select the name from the list that appears. Or, select Formulas > Use in Formula...
Read more >Chapter 6 Simulation Flashcards | Quizlet
Enter a formula in cell F2 using SUMIFS to calculate the total expense (use the named range Cost) where the value in the...
Read more >How to Create and Use Excel Named Ranges - Contextures
Create Excel names that refer to cells, a constant value, or a formula. Use names in formulas, or quickly select a named range....
Read more >Transcripts and Recordings of Oral Arguments - Supreme Court
Transcripts for oral arguments prior to October Term 2000 have been scanned ... The recordings will be listed by case name, the docket...
Read more >Cell Multiplexing with cellranger multi -Software - Support
The [gene-expression] section has two columns that specify parameters relevant to analysis of gene expression data, such as reference genome and cell-calling ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Okay – but if not
supercell
then I think thatcell
is the only other reasonable option (that I can think of). The existingcell
should then be removed in favor of theCell
object. I can see thatobj.cell.cell
is weird, maybeobj.cell.basis
orobj.cell.vectors
(orabc
, as you suggested yourself) is better then? Possibly putting an alias intoCellChild
(that I just realized existed!) via@property
so that the matrix can be accessed directly viacellchild.basis
or whichever.I am beginning to be more keen on using
Lattice
, it is short! 👍