Neumann's Principle and Curie laws

Neumann‘s Principle

Neumann‘s principle, or principle of symmetry, states that, if a crystal is invariant with respect to certain symmetry elements, any of its physical properties must also be invariant with respect to the same symmetry elements, or otherwise stated, the symmetry elements of any physical property of a crystal must include the symmetry elements of the point group of the crystal. It is generalized to physical phenomena by Curie laws.

Example

This principle may be illustrated by considering the optical indicatrix of a crystal, which is an ellipsoid. If the medium is invariant with respect to a three-fold, a four-fold or a six-fold axis (as in a trigonal, tetragonal or hexagonal crystal, for instance), its optical indicatrix must also be invariant with respect to the same axis, according to Neumann‘s principle. As an ellipsoid can only be ordinary or of revolution, the indicatrix of a trigonal, tetragonal or hexagonal crystal is necessarily an ellipsoid of revolution. These crystals are said to be uniaxial. In a cubic crystal which has four three--fold axes, the indicatrix must have several axes of revolution, it is therefore a sphere and cubic media behave as isotropic media for properties represented by a tensor of rank 2.

Curie laws

Curie extended the notion of symmetry to include that of physical phenomena and stated that:

  • the symmetry characteristic of a phenomenon is the highest compatible with the existence of the phenomenon;
  • the phenomenon may exist in a medium which possesses that symmetry or that of a subgroup of that symmetry.

and concludes that some symmetry elements may coexist with the phenomenon but that their presence is not necessary. On the contrary, what is necessary is the absence of certain symmetry elements: ‘asymmetry creates the phenomenon’. Noting that physical phenomena usually express relations between a cause and an effect (an influence and a response), P. Curie restated the two above propositions in the following way, now known as Curie laws, although they are not, strictly speaking, laws (Curie himself spoke about ‘the principle of symmetry‘):

  • the asymmetry of the effects must pre-exist in the causes;
  • the effects may be more symmetric than the causes.

Applications

Curie applied the above statements to determine the symmetry characteristic of physical quantities such as a polar vector, a force or an electrical field, A ∞M, an axial vector or a magnetic field, (A /MC.

If one now considers a phenomenon resulting from the superposition of several causes in the same medium, one may note that the symmetry of the global cause is the intersection of the groups of symmetry of the various causes: the asymmetries add up. This remark can be applied to the determination of the point groups where physical properties such as pyroelectricity or piezoelectricity are possible.

References:

[1] Franz Neumann (1795-1898)‘s principle was first stated in his course at the university of K?nigsberg (1873/1874) and was published in the printed version of his lecture notes (Neumann F.E., 1885, Vorlesungen über die Theorie der Elastizit?t der festen K?rper und des Licht?thers, edited by O. E. Meyer. Leipzig, B. G. Teubner-Verlag.

[2] Pierre Curie (1859-1906)‘s principle of symmetry is stated in Curie P., 1894, J. Physique3, 393-415, Sur la symétrie dans les phénomènes physiques, symétrie d‘un champ électrique et d‘un champ magnétique.

[3] https://Chemistry/Crystallography/PhysicalPropertiesCrystals/NeumannPrinciple

[4] http://oldwww.iucr.org/iucr-top/comm/cteach/pamphlets/18/node4.html

[5] http://reference.iucr.org/dictionary/Neumann%27s_principle

Neumann's Principle and Curie laws

时间: 2024-10-10 08:57:02

Neumann's Principle and Curie laws的相关文章

Linux Kernel Module(LKM) Init、Delete Code Principle Learning

目录 1. Linux模块(LKM)简介 2. 使用Linux模块 3. LKM模块加载原理 4. LKM模块卸载原理 1. Linux模块(LKM)简介 模块是一种向linux内核添加"设备驱动程序"."文件系统"."其他组件"的有效方法,而无须重新编译内核或重启系统,这消除了许多限制,同时带来了很多的优点 1. 通过使用模块,内核程序员能够预先编译大量驱动程序,而不会致使内核映像的尺寸发生膨胀.在自动检测硬件或用户提示后,安装例程会选择适当的

Linux /proc、/dev Principle Learning

目录 1. /proc简介 2. 内核机制相关 3. 进程信息 4. 硬件设备相关 5. 系统信息 6. /dev简介 1. /proc简介 在linux的根目录下有一个/proc目录,/proc文件系统是一个虚拟文件系统,通过它可以使用一种新的方法在Linux内核空间和用户空间之间进行通信.在/proc文件系统中,我们可以将对虚拟文件的读写作为与内核中实体进行通信的一种手段,但是与普通文件不同的是,这些虚拟文件的内容都是动态创建的(即在我们执行指令的那一刹那才产生的) /proc文件系统包含了

C#设计模式系列:单一职责原则(Single Responsibility Principle)

1.单一职责原则的核心思想 一个类应该有且只有一个变化的原因. 2.为什么要引入单一职责原则 单一职责原则将不同的职责分离到单独的类,每一个职责都是一个变化的中心.当需求变化时,这个变化将通过更改职责相关的类来体现.如果一个类拥有多于一个的职责,则这些职责就耦合到在了一起,那么就会有多于一个原因来导致这个类的变化.对于某一职责的更改可能会损害类满足其他耦合职责的能力.这样职责的耦合会导致设计的脆弱,以至于当职责发生更改时产生无法预期的破坏. 3.单一职责原则的优点 1>.可以降低类的复杂度,一个

里氏替换原则(Liskov Substitution Principle)

开放封闭原则(Open Closed Principle)是构建可维护性和可重用性代码的基础.它强调设计良好的代码可以不通过修改而扩展,新的功能通过添加新的代码来实现,而不需要更改已有的可工作的代码.抽象(Abstraction)和多态(Polymorphism)是实现这一原则的主要机制,而继承(Inheritance)则是实现抽象和多态的主要方法. 那么是什么设计规则在保证对继承的使用呢?优秀的继承层级设计都有哪些特征呢?是什么在诱使我们构建了不符合开放封闭原则的层级结构呢?这些就是本篇文章将

接口隔离原则(Interface Segregation Principle)ISP

using System; using System.Collections.Generic; using System.Text; namespace InterfaceSegregationPrinciple { //接口隔离原则(Interface Segregation Principle)ISP //Clients should not be forced to depend upon interfaces that they don's use.(客户端不应该依赖它不需要的接口) /

里氏替换原则(Liskov Substitution Principle) LSP

using System; using System.Collections.Generic; using System.Text; namespace LiskovSubstitutionPrinciple { //里氏替换原则(Liskov Substitution Principle) LSP //If for each object o1 of type S there is an object o2 of type T such that for all programs P defi

设计模式六大原则(2):里氏替换原则(Liskov Substitution Principle)

肯定有不少人跟我刚看到这项原则的时候一样,对这个原则的名字充满疑惑.其实原因就是这项原则最早是在1988年,由麻省理工学院的一位姓里的女士(Barbara Liskov)提出来的. 定义1:如果对每一个类型为 T1的对象 o1,都有类型为 T2 的对象o2,使得以 T1定义的所有程序 P 在所有的对象 o1 都代换成 o2 时,程序 P 的行为没有发生变化,那么类型 T2 是类型 T1 的子类型. 定义2:所有引用基类的地方必须能透明地使用其子类的对象. 问题由来:有一功能P1,由类A完成.现需

设计模式六大原则(4):接口隔离原则(Interface Segregation Principle)

接口隔离原则: 使用多个专门的接口比使用单一的总接口要好. 一个类对另外一个类的依赖性应当是建立在最小的接口上的. 一个接口代表一个角色,不应当将不同的角色都交给一个接口.没有关系的接口合并在一起,形成一个臃肿的大接口,这是对角色和接口的污染. "不应该强迫客户依赖于它们不用的方法.接口属于客户,不属于它所在的类层次结构."这个说得很明白了,再通俗点说,不要强迫客户使用它们不用的方法,如果强迫用户使用它们不使用的方法,那么这些客户就会面临由于这些不使用的方法的改变所带来的改变. 定义:

“开-闭”原则 (Open-Closed principle, OCP)

"开-闭"原则 (Open-Closed principle, OCP) 一个软件实体应当对扩展开放,对修改关闭. Software entities should be open for extension, but closed for modification. 在设计一个模块的时候,应当使这个模块可以在不被修改的前提下被扩展. "可变性的封装原则"从工程的角度讲解了如何实现"开-闭"原则. "可变性的封装原则"意味着两