Update to the Neutrino-Electron Scattering in Left-Right Symmetric Models

electron autoupdater releasenotes “Electron自动更新器发布说明”随着技术的不断发展，软件更新已经成为用户体验中重要的一环。

为了简化软件更新流程并提供更好的用户体验，Electron开发团队推出了Electron自动更新器。

本文将一步一步回答关于该自动更新器的问题，详细介绍其特性和使用方法。

第一步：什么是Electron自动更新器？Electron自动更新器是一个用于Electron应用程序的开源工具，它允许开发人员自动更新其应用程序的版本。

通过自动检查可用的更新，并为用户提供下载和安装更新的选项，开发人员可以轻松地使他们的应用程序保持最新。

第二步：Electron自动更新器的主要特性有哪些？Electron自动更新器具有以下主要特性：1. 自动检查更新：自动更新器会定期检查可用的更新，并在发现新版本时通知用户。

2. 后台下载：自动更新器可以在后台下载更新文件，不会干扰用户对应用程序的使用。

3. 断点续传：如果下载过程中出现网络中断或其他问题，自动更新器支持断点续传，确保下载的完整性。

4. 安装选项：一旦下载完成，自动更新器会为用户提供安装选项，以便他们可以自由选择何时安装更新。

5. 下载进度通知：自动更新器会显示下载进度，以提供用户更新的实时状态。

6. 更新日志展示：自动更新器可以显示更新日志，让用户了解新版本的改进和修复的问题。

第三步：如何在Electron应用程序中使用自动更新器？要在Electron应用程序中使用自动更新器，您可以按照以下步骤进行设置：1. 安装electron-updater包：在您的Electron项目中，使用npm或yarn安装electron-updater包。

2. 配置自动更新器：在主进程（main.js）文件中配置自动更新器，指定更新内容和更新服务器的URL。

3. 定义自动更新的策略：您可以定义自动更新的频率和方式，例如启动应用程序时自动检查更新或用户手动触发更新。

1、打开Neurosolutions,进入以下界面值点击NS Excel '按钮，在Excel 加载项中出现Neurosolutions 项。

者文件封 硝如 祖眼⑵ 插入⑴ 梏式约 工具。

的据此 窗口口 增助如 咯1171t :加口与0昌国导融X 。

息-W g 》包£1曲鼬？宋^2、标记数据选定指标数据列(x1 x5),点击Neurosolutions 菜单选择Tag Data 下Column(s) As Input 选 项，将(x1 x5)标记为输入。

选定指标数据列y,点击Tag Data 下Column(s) As Desired 选 项，将y 标记为输出。

选定第1到53个样本所在的行，点击Tag Data 下Row(s) As Training 选项，将其标记为训练集。

最后选定第53到58个样本所在的行，点击Tag Data 下Row(s) As Testing 选项，将其标记为测试集。

标记完成后界面如下。

力文杵0 ««'E：'福图也人工I 格加0 IM'I)她存艰 营口的 也助如 乐u&LW.a 口片& 寻&晶怪五，U M 唾些 I ：**磔3、预处理数据点击Neurosolutions 菜单，选择Preprocess Data 下Randomize Rows 选项，完成数据处理， Excel 出现 sheet1Randomize.亘］交件区i锚强£J次困以置入UJ格式®।IflCU 窈竟亚।宙口-J黜助皿Heur由IxLi皿□N kl 目鼻咎EL占心T ,他E TIMIB鄱B：^:、B c0E F:H I■2 4U71334QB95q 4峥95 4U6928 4069T7S40G939 4067&IO4Ci?1711407051245r o 913iUB&il1440&E21540719IE4U70617口 ,一16：'■''1940BBD如4涮521406B32240679Z3 4Q&7B.:;4U71D2E-40705EE 407 IS274067E.ME4、建立BP神经网络模型选择Excel的sheetl工作表界面，点击Neurosolutions菜单，选择Create/Open Network下的New Custom Network选项，出现以下界面。

MaterialsStudio2021新版本发布｜达索系统Materials Studio 2021增加一系列面向产品研发的新功能，进一步扩展了在热门研究领域的应用能力，包括在新功能材料和能源材料方面。

Materials Studio 新功能•新模块FlexTS，FlexTS为DMol3和DFTB+提供了在势能面上找到固定点的任务功能，使计算反应路径和与化学反应相关的能垒成为可能。

Materials Studio Collection基于Pipeline Pilot新增的系列protocols，采用PhaseField计算硬质材料的硬化和晶粒生长。

用户可在Materials Studio的Pipeline Pilot Connector中访问Metal Alloy文件夹，并使用上述protocols。

Materials Studio提供两个相关案例，介绍上述protocols使用方法。

Forcite和Mesocite计算中可使用GPU加速，同时可提交GPU任务到任何支持的排队系统中。

Materials Studio 各模块增强功能1、Cantera•Cantera升级到2.4.0版本，Python升级到3.8.1。

2、CASTEP1.在CASTEP的弹性常数计算结果中加入了Niu等（2019）的材料断裂韧度估算经验模型，预测脆性材料性质。

CASTEP现可计算孤立分子的溶剂化能。

在CASTEP中实现了二次谐波产生系数张量的计算，有助于开发非线性光学材料。

CASTEP中增加了自发极化的Berry phase计算方法。

CASTEP中的自旋轨道耦合计算现已扩展到：动态产生的norm-conserving赝势。

光学性质计算。

支持使用非局域交换关联泛函。

在Materials Visualizer中设置非共线自旋构型。

3、COMPASS•COMPASSIII支持与锂离子电池相关的硼化物，例如双（草酸）硼酸盐、二氟（草酸）硼酸盐和吡啶三氟化硼的计算。

文件编号：NPS-CT-0019归属部门：服务创新部保密等级：秘密Neuviz 64软件1.0.4升级指导书活动签名/日期部门/职务编制陆瑶2013.1.9 服务创新部/工程师审核莫晓明2013.1.9 服务创新部/部长田洪宇2013.1.9 国内服务部/部长批准王志强2013.1.10 服务运营中心/总监实施日期 2013年1月10日沈阳东软医疗系统有限公司NEUSOFT MEDICAL SYSTEMS CO., LTD.1 目的指导现场工程师更好的执行FCO-CT-12-004，完成软件升级到1.0.42 范围Neuviz 64e/Neuviz 64i 软件v1.0.4以下版本3 职责国内服务部现场服务工程师负责FCO升级的实施。

4 内容及方法4.1 执行FCO-CT-12-004注意事项4.1.1 主控台，建像机，AVW工作站操作系统升级时，需重新安装windows操作系统（2.0.2版本），安装系统之前需备份系统信息。

在重新安装时，切忌不要对整个硬盘进行操作，这样会造成患者数据丢失，只需安装操作系统即可。

4.1.2 1.0.4版本主控台与Gantry连接的IP改为212段，安装新版操作系统即可自动设置。

Host计算机的Gantry端口的IP为192.168.212.10。

4.1.3进行1.0.4升级时， Ucom板无法使用软件自动升级功能。

自动升级FPGA之前需手动升级UCOM板的Firmware；需要手动升级CTBOX，控制台转接板的Firmware，呼吸道航板。

4.1.4 1.0.4版本主控台和AVW工作站服务用户登录软件或使用服务功能和服务工具需要用到Service Ukey。

4.2 工具及物料工具：FSE标准工具包Xilinx下载电缆1条Ucom下载电缆1条跳线帽1个AVR下载电缆1条CF读卡器1个USB接口移动光驱1台Service Ukey（需预先完成Service Ukey的注册和激活参考“Service Ukey操作指南”，Service Ukey的申请）1个软件升级套件：Neuviz 64 Host OS 2.0.2 光盘（96200163）1张Neuviz 64 Recon OS 2.0.2 光盘（96200173）1张AVW OS 2.0.2 光盘（96200203）1张软件安装包及服务工具包括Neuviz 64 Software Install 1.0.4（96200188）；AVW Software Install（96200218）；Neuviz 64 Service tools (96200196）；Service Ukey tools（96201011）；AVR，xilinx等下载电缆工具软件在一张光盘内1张空白光盘3张4.3 升级步骤软件版本为1.0.4以下版本，执行FCO-CT-12-004升级。

Release NotesTABLE OF CONTENTS Chapter 1. Release Notes (1)1.1. Updates in 2023.3.1 (1)1.2. Updates in 2023.3 (1)1.3. Updates in 2023.2.1 (2)1.4. Updates in 2023.2 (2)1.5. Updates in 2023.1.1 (2)1.6. Updates in 2023.1 (3)1.7. Updates in 2022.4.1 (3)1.8. Updates in 2022.4 (3)1.9. Updates in 2022.3 (3)1.10. Updates in 2022.2.1 (4)1.11. Updates in 2022.2 (4)1.12. Updates in 2022.1.1 (4)1.13. Updates in 2022.1 (4)1.14. Updates in 2021.3.1 (4)1.15. Updates in 2021.3 (5)1.16. Updates in 2021.2.3 (5)1.17. Updates in 2021.2.2 (5)1.18. Updates in 2021.2.1 (5)1.19. Updates in 2021.2 (5)1.20. Updates in 2021.1.1 (6)1.21. Updates in 2021.1 (6)1.22. Updates in 2020.3.1 (6)1.23. Updates in 2020.3 (6)1.24. Updates in 2020.2.1 (6)1.25. Updates in 2020.2 (6)1.26. Updates in 2020.1.2 (7)1.27. Updates in 2020.1.1 (7)1.28. Updates in 2020.1 (7)1.29. Updates in 2019.1 (7)Chapter 2. Known Limitations (8)Chapter 3. Known Issues (9)Chapter 4. Support (10)4.1. Platform Support (10)4.2. GPU Support (10)LIST OF TABLES T able 1 Platforms supported by Compute Sanitizer (10)1.1. Updates in 2023.3.1‣Fixed error output for WGMMA instructions.1.2. Updates in 2023.3‣Added support for Heterogeneous Memory Management (HMM) and Address Translation Service (ATS). The feature is opt-in using the --hmm-supportcommand-line option.‣Added racecheck support for device graph launches.‣Added the ability to suppress known issues using the --suppressions command-line option. See the suppressions documentation for more information.‣Added support for external memory objects. This effectively adds support for Vulkan and D3D12 interop.‣Added device backtrace support for WSL.‣Improve PC offset output. It is now printed next to the function name to clarify it is an assembly offset within that function.‣Several command-line options no longer require to explicitly specify "yes" or "no"when they are used.‣Renamed the options --kernel-regex and --kernel-regex-exclude to --kernel-name and --kernel-name-exclude.‣Added the regex filtering key to --kernel-name and --kernel-name-exclude.‣Added new command-line option --racecheck-indirect-barrier-dependency to enable indirect cuda::barrier tracking in racecheck.‣Added new command-line option --coredump-behavior to control the target application behavior after generating a GPU coredump.‣Added new command-line option --detect-missing-module-unload to detect missing calls to the cuModuleUnload driver API.‣Added new command-line option --preload-library to make the target application load a shared library before the injectiion libraries.‣Fix initcheck false positive when memory loads are widened and include padding bytes.‣Fix potential hang in racecheck and synccheck tools when the bar.arrive instruction is used.‣Added patching API support for the setsmemsize instruction.‣Added patching API support for __syncthreads() after the barrier is released.1.3. Updates in 2023.2.1‣Fixed potential racecheck hang on H100 when using thread block clusters.‣Compute Sanitizer 2023.2.1 is incorrectly versioned as 2023.2.0 and need to be differentiated by its build ID 33053471.1.4. Updates in 2023.2‣Added support for CUDA device graph launches.‣Added racecheck support for cluster entry and exit race detection for remote shared memory accesses. See the cluster entry and exit race detection documentation for more information.‣Added support for CUDA lazy loading when device heap checking is enabled.Requires CUDA driver version 535 or newer.‣Added support for tracking child processes launched with system() orposix_spawn(p) when using --target-processes all.‣Added support for st.async and red.async instructions.‣Improved support for partial warp synchronization using cooperative groups in racecheck.‣Improved support for cuda::barrier::wait() on SM 9.x.‣Added coredump support for Pascal architecture and multi-context applications.‣Added support for OptiX 8.0.‣Improved performance when using initcheck in OptiX applications in some cases.Using initcheck to track OptiX applications now requires the option --check-optix yes.1.5. Updates in 2023.1.1‣Fixed bug where memcheck would report out-of-bound accesses when loading user parameter values using a ternary operator.‣Fixed potential crash when using leakcheck with applications using CUBLAS.‣Fixed potential false positives when using synccheck or racecheck with applications using CUDA barriers.1.6. Updates in 2023.1‣Added racecheck support for distributed shared memory.‣Extended stream-ordered race detection to cudaMemcpy APIs.‣Added memcheck, synccheck and patching API support for warpgroup operations.‣Added --coredump-name CLI option to set the coredump file name.‣Added support for Unicode file paths.‣Added support for OptiX 7.7.1.7. Updates in 2022.4.1‣Fixed bug where synccheck would incorrectly report illegal instructions for code using cluster.sync() and compiled with --device-debug‣Fixed incorrect address reports in SanitizerCallbackMemcpyAsync in some specific cases, leading to potential invalid results in memcheck and racecheck.‣Fixed potential hangs and invalid results with racecheck on OptiX applications.‣Fixed potential crash or invalid results when using CUDA Lazy Module Loading with memcheck or initcheck if --check-device-heap is enabled. Lazy Module Loading will be automatically disabled in these cases.1.8. Updates in 2022.4‣Added support for __nv_aligned_device_malloc.‣Added support for ldmatrix and stmatrix instructions.‣Added support for cache control operations when using the --check-cache-control command-line option.‣Added new command-line option --unused-memory-threshold to control the threshold for unused memory reports.‣Improved support for CUDA pipeline memcpy-async related hazards in racecheck.1.9. Updates in 2022.3‣Added support for the NVIDIA GH100/SM 9.x GPU architecture.‣Added support for the NVIDIA AD10x/SM 8.9 GPU architecture.‣Added support for lazy kernel loading.‣Added memcheck support for distributed shared memory.‣Added new options --num-callers-device and --num-callers-host to control the number of callers to print in stack traces.‣Added support for OptiX 7.6 applications.‣Fix bug on Linux ppc64le where the host stack trace was incomplete.1.10. Updates in 2022.2.1‣Fixed incorrect device backtrace for applications compiled with -lineinfo.1.11. Updates in 2022.2‣Added memcheck support for use-before-alloc and use-after-free race detection. See the stream-ordered race detection documentation for more information.‣Added leakcheck support for asynchronous allocations, OptiX resources and CUDA memmap (on Linux only for the latter).‣Added option to ignore CUDA_ERROR_NOT_FOUND error codes returned by the cuGetProcAddress API.‣Added new sanitizer API functions to allocate and free page-locked host memory.‣Added sanitizer API callbacks for the event management API.1.12. Updates in 2022.1.1‣Fixed initcheck issue where the tool would incorrectly abort a CUDA kernel launch after reporting an uninitialized access on Windows with hardware schedulingenabled.1.13. Updates in 2022.1‣Added support for generating coredumps.‣Improved support for stack overflow detection.‣Added new option --target-processes-filter to filter the processes being tracked by name.‣Added initcheck support for asynchronous allocations. Requires CUDA driver version 510 or newer.‣Added initcheck support for accesses on peer devices. Requires CUDA driver version 510 or newer.‣Added support for OptiX 7 applications.‣Added support for tracking the child processes of 32-bit processes in multi-process applications on Linux and Windows x86_64.1.14. Updates in 2021.3.1‣Fixed intermittent issue on vGPU where synccheck would incorrectly detect divergent threads.‣Fixed potential hang when tracking several graph launches.1.15. Updates in 2021.3‣Improved Linux host backtrace.‣Removed requirement to call cudaDeviceReset() for accurate reporting of memory leaks and unused memory features.‣Fixed synccheck potential hang when calling __syncthreads in divergent code paths on Volta GPUs or newer.‣Added print of nearest allocation information for memcheck precise errors in global memory.‣Added warning when calling device-side malloc with an empty size.‣Added separate sanitizer API device callback for cuda::memcpy_async.‣Added new command-line option --num-cuda-barriers to override the expected number of cuda::barrier used by the target application.‣Added new command-line options --print-session-details to print session information and --save-session-details to save it to the output file.‣Added support for WSL2.1.16. Updates in 2021.2.3‣Enabled SLS hardening and branch protection for L4T builds.1.17. Updates in 2021.2.2‣Enabled stack canaries with random canary values for L4T builds.1.18. Updates in 2021.2.1‣Added device backtrace for malloc/free errors in CUDA kernels.‣Improved racecheck host memory footprint.1.19. Updates in 2021.2‣Added racecheck and synccheck support for cuda::barrier on Ampere GPUs or newer.‣Added racecheck support for __syncwarp with partial mask.‣Added --launch-count and --launch-skip filtering options. See the Command Line Options documentation for more information.‣--filter and --exclude options have been respectively renamed to --kernel-regex and --kernel-regex-exclude.‣Added support for QNX and Linux aarch64 platforms.‣Added support for CUDA graphs memory nodes.1.20. Updates in 2021.1.1‣Fixed an issue where incorrect line numbers could be shown in errors reports.1.21. Updates in 2021.1‣Added support for allocation padding via the --padding option.‣Added experimental support for NVTX memory API using option --nvtx yes.Please refer to NVTX API for Compute Sanitizer Reference Manual for moreinformation.1.22. Updates in 2020.3.1‣Fixed issue when launching a CUDA graph multiple times.‣Fixed false positives when using cooperative groups synchronization primitives with initcheck and synccheck.1.23. Updates in 2020.3‣Added support for CUDA memory pools and CUDA API reduced serialization.‣Added host backtrace for unused memory reports.1.24. Updates in 2020.2.1‣Fixed crash when loading cubins of size larger than 2 GiB.‣Fixed error detection on systems with multiple GPUs.‣Fixed issue when using CUDA Virtual Memory Management API cuMemSetAccess to remove access to a subset of devices on a system with multiple GPUs.‣Added sanitizer API to translate between sanitizer and CUDA stream handles.1.25. Updates in 2020.2‣Added support for CUDA graphs and CUDA memmap APIs.‣The memory access callback of the sanitizer API has been split into three distinct callbacks corresponding to global, shared and local memory accesses.Release Notes 1.26. Updates in 2020.1.2‣Added sanitizer stream API. This fixes tool crashes when per-thread streams are being used.1.27. Updates in 2020.1.1‣Added support for Windows Hardware-accelerated GPU scheduling‣Added support for tracking child processes spawned by the application launched under the tool via the --target-processes CLI option.1.28. Updates in 2020.1‣Initial release of the Compute Sanitizer (with CUDA 11.0)Updates to the Sanitizer API :‣Added support for per-thread streams‣Added APIs to retrieve the PC and size of a CUDA function or patch‣Added callback for cudaStreamAttachMemAsync‣Added direction to memcpy callback data‣Added stream to memcpy and memset callbacks data‣Added launch callback after syscall setup‣Added visibility field to allocation callback data‣Added PC argument to block entry callback‣Added incoming value to memory access callbacks‣Added threadCount to barrier callbacks‣Added cooperative group flags for barrier and function callbacks1.29. Updates in 2019.1‣Initial release of the Compute Sanitizer API (with CUDA 10.1)‣Applications run much slower under the Compute Sanitizer tools. This may cause some kernel launches to fail with a launch timeout error when running with the Compute Sanitizer enabled.‣Compute Sanitizer tools do not support device backtrace on Maxwell devices (SM5.x).‣Compute Sanitizer tools do not support coredumps on WSL2.‣The memcheck tool does not support CUDA API error checking for API calls made on the GPU using dynamic parallelism.‣The racecheck, synccheck and initcheck tools do not support CUDA dynamic parallelism.‣CUDA dynamic parallelism is not supported when Windows Hardware-accelerated GPU scheduling is enabled.‣Compute Sanitizer tools cannot interoperate with other CUDA developer tools.This includes CUDA coredumps which are automatically disabled by the Compute Sanitizer. They can be enabled instead by using the --generate-coredump option.‣Compute Sanitizer tools do not support IPC memory pools. Using it will result in false positives.‣Compute Sanitizer tools are not supported when SLI is enabled.‣The racecheck tool may print incorrect data for "Current value" when reporting a hazard on a shared memory location where the last access was an atomic operation.This can also impact the severity of this hazard.‣On QNX, when using the --target-processes all option, analyzing shell scripts may hang after the script has completed. End the application using Ctrl-C on the command line in that case.‣The initcheck tool might report false positives for device-to-host cudaMemcpy operations on padded structs that were initialized by a CUDA kernel. The #pragma pack directive can be used to disable the padding as a workaround.‣When a hardware exception occur during a kernel launch that was skipped due to the usage of the kernel-name, kernel-name-exclude, launch-count or launch-skip options, the memcheck tool will not be able to report additionaldetails as an imprecise error.‣The leakcheck feature is disabled under Confidential Computing.Information on supported platforms and GPUs.4.1. Platform SupportT able 1 Platforms supported by Compute Sanitizer4.2. GPU SupportThe compute-sanitizer tools are supported on all CUDA capable GPUs with SM versions 5.0 and above.NoticeALL NVIDIA DESIGN SPECIFICATIONS, REFERENCE BOARDS, FILES, DRAWINGS, DIAGNOSTICS, LISTS, AND OTHER DOCUMENTS (TOGETHER AND SEPARATEL Y, "MATERIALS") ARE BEING PROVIDED "AS IS." NVIDIA MAKES NO WARRANTIES, EXPRESSED, IMPLIED, STATUTORY, OR OTHERWISE WITH RESPECT TO THE MATERIALS, AND EXPRESSL Y DISCLAIMS ALL IMPLIED WARRANTIES OF NONINFRINGEMENT, MERCHANTABILITY, AND FITNESS FOR A PARTICULAR PURPOSE.Information furnished is believed to be accurate and reliable. However, NVIDIA Corporation assumes no responsibility for the consequences of use of such information or for any infringement of patents or other rights of third parties that may result from its use. No license is granted by implication of otherwise under any patent rights of NVIDIA Corporation. Specifications mentioned in this publication are subject to change without notice. This publication supersedes and replaces all other information previously supplied. NVIDIA Corporation products are not authorized as critical components in life support devices or systems without express written approval of NVIDIA Corporation.TrademarksNVIDIA and the NVIDIA logo are trademarks or registered trademarks of NVIDIA Corporation in the U.S. and other countries. Other company and product names may be trademarks of the respective companies with which they are associated. Copyright© 2019-2023 NVIDIA Corporation and affiliates. All rights reserved.This product includes software developed by the Syncro Soft SRL (http:// www.sync.ro/).。

在没有考虑vdw作用之前，算Bi2Se3材料soc中出现的错误汇总V ASP自旋轨道耦合计算错误汇总静态计算时，报错：VERY BAD NEWS! Internal内部error in subroutine子程序IBZKPT:Reciprocal倒数的lattice and k-lattice belong to different class of lattices. Often results are still useful (48)INCAR参数设置：对策：根据所用集群，修改INCAR中NPAR。

将NPAR=4变成NPAR=1，已解决！错误：sub space matrix类错误报错：静态和能带计算中出现警告：W ARNING: Sub-Space-Matrix is not hermitian共轭in DA V结构优化出现错误：WARNING: Sub-Space-Matrix is not hermitian in DA V 4 -4.681828688433112E-002对策：通过将默认AMIX=0.4，修改成AMIX=0.2（或0.3），问题得以解决。

以下是类似的错误：WARNING: Sub-Space-Matrix is not hermitian in rmm -3.00000000000000RMM: 22 -0.167633596124E+02 -0.57393E+00 -0.44312E-01 1326 0.221E+00BRMIX:very serious problems the old and the new charge density differ old charge density: 28.00003 new 28.06093 0.111E+00错误：WARNING: Sub-Space-Matrix is not hermitian in rmm -42.5000000000000ERROR FEXCP: supplied Exchange-correletion table is too small, maximal index : 4794错误：结构优化Bi2Te3时，log文件：WARNING in EDDIAG: sub space matrix is not hermitian 1 -0.199E+01RMM: 200 0.179366581305E+01 -0.10588E-01 -0.14220E+00 718 0.261E-01BRMIX: very serious problems the old and the new charge density differ old charge density: 56.00230 new 124.70394 66 F= 0.17936658E+01 E0= 0.18295246E+01 d E =0.557217E-02curvature: 0.00 expect dE= 0.000E+00 dE for cont linesearch 0.000E+00ZBRENT: fatal error in bracketingplease rerun with smaller EDIFF, or copy CONTCAR to POSCAR and continue但是，将CONTCAR拷贝成POSCAR，接着算静态没有报错，这样算出来的结果有问题吗？对策1：用这个CONTCAR拷贝成POSCAR重新做一次结构优化，看是否达到优化精度！对策2：用这个CONTCAR拷贝成POSCAR，并且修改EDIFF（目前参数EDIFF=1E-6）,默认为10-4错误：WARNING: Sub-Space-Matrix is not hermitian in DA V 1 -7.626640664998020E-003网上参考解决方案：对策1：减小POTIM: IBRION=0，标准分子动力学模拟。

·28·20182-12Extracting Nuclear form Factors with CoherentNeutrino Scattering∗E.Ciuffoli,J.Evslin,Q.Fu,H.Mohammed and J.TangThis year we continued to study experiments that can be performed using neutrinos produced via Decay At Rest(DAR)at spallation sources.In2017the COHERENT collaboration was able to measure for thefirst time Coherent Elastic Neutrino Nucleus Scattering(CENNS)[1]:neutrinos are produced at the Spallation Neutruon Source(SNS)via Pion Decay At Rest(πDAR).The study on CENNS brings us to a new precision era:first of all,any deviation from the Standard Model prediction can be a sign of new physics;moreover,neutrino-nucleus interactions are crucial in the understating of core collapse supernovae,and information on the CENNS cross sec-tion can be useful for the next generation dark matter detectors,since they are rapidly approaching to the intrinsic neutrino backgroundfloor.From CENNS it is also possible to obtain important information on the electroweak form factor and on the neutron distribution inside the nucleus.In collaboration with prof.Jian Tang,from SYSU, we studied the precision that can be achieved in this kind of experiment,as a function of the detector mass and using different assumptions on the steady-state background and on the systematic errors.We found that the low-energy threshold has little effect on thefinal result,since most of the information on the form factor comes from the high-energy tail of the spectrum;however in order to measure precisely the neutron radius a very good precision on the quenching factor(QF)is required.We used the Helm model to describe the neutron distribution inside the nucleus,and the precision of the experiment was defined as the1-sigma error on the parameters of such a model. From the observation of CENNS it is also possible to obtain a model-independent estimation of the momenta of the neutron distribution:indeed,if the form factor is expanded as a power series,each term Q2n is multipled by a factor proportional to the2n-th momentum the neutron distrubution⟨R2n⟩;the precision that can be possible to achieved using this approach was computed.We calculated also theπDAR rate as a function of the accelerator energy:it is possible to run such an experiment using neutrinos that will be produced at ADS facilities,however since there the beam will be not pulsed,a very good veto system must be implemented to reduce the steady state background;such an experiment can also be run using the neutrinos produced at China Spallation Neutron Source (CSNS).These results were published in Ref.[2]and presentented at several international conferences(Fig.1).Fig.1(color online)Expected precision at CSNS(1ton detector,1year running time)using a liquid Argon and liquid Xenon detectors.Dashed curves:1%uncertainty on the QF;solid curves:perfect knowledge of QF assumed.References[1] D.Akimov,(COHERENT Collaboration),Science,357(2017)1123.[2] E.Ciuffoli,J.Evslin,Q.Fu,et al.,Phys.Rev.D,97(2018)113003.[3] E.Ciuffoli,“Extracting Nuclear Form Factors from Coherent Neutrino Scattering”,Neutrino2018,4-9June2018,Heidelberg(DE),2018·29·DOI:10.5281/zenodo.1300739.[4] E.Ciuffoli,“Measuring the Neutron Distribution from Coherent Elastic Neutrino Nucleus Scattering”,NuPhys2018,19-21Decem-ber2018,London(UK).∗Foundation item:Chinese Academy of Sciences Presidents International Fellowship Initiative(2015PM063),National Natural Science Foundation of China(11375201),CAS Key Research Program of Frontier Sciences(QYZDY-SSW-SLH006)and Recruitment Program of High-end Foreign Experts2-13A Role of Angular Momentum of Electron inAharonov-Bohm Effect∗Yoshio Kitadono,Zou Liping and Zhang PengmingAharonov-Bohm(AB)effect[1]shows one of surprising aspects of gaugefield in quantum electrodynamics(QED). In classical electrodynamics,the gauge potentials A0(t,x),A(t,x)appear in the middle of calculations.However,final results for observables are only expressed by the electromagneticfield E(t,x),B(t,x).They are related to each other through the relations,E(t,x)=−∇A0(t,x)−∂t A(t,x),B(t,x)=∇×A(t,x).One can say that the physical quantity is the electromagneticfield,meanwhile the gauge potentials are useful mathematical tools to derive the physical quantities,at least in classical electrodynamics.Aharonov and Bohm showed that two electron beams passing along the infinitely long solenoid experience the interference at the screen after the two separated beams are reunified.The phase shift of the interferenceΦwas given inΦ≡e|x|=R A(x)·d x=e∫∫S(∇×A(x))=πR2eB,(1)where R is a radius of the solenoid,B is the magneticfield induced inside of the solenoid,e is the electron’s charge, and S is the sphere covering the solenoid.The above result is completely written by the magneticfield which is the gauge invariant quantity and hence there is no inconsistency with the gauge principle.However,the problem arises in the physical interpretation of this phenomenon,i.e.it looks that the electron beams seem to be affected by the non-zero gauge potential as a physical entity outside of the solenoid. Otherwise,it looks that the magneticfield inside of the solenoid remotely affects the electron beam outside of the solenoid.However,both interpretation contradict to our standard knowledge of the ually we consider this phenomena in the following.The gauge potential itself is not observed in this experiment,despite it looks like a physical entity affecting the electron.The observable is the line integral in Eq.(1).We took this system to analyse the role of the electron’s orbital angular momentum(OAM)in the AB effect[2]. The OAM is recently discussed in the context of the nucleon spin problem[3].One of the advantage of this system is that many analytical aspects are already known and hence it is good to investigate the role of the electron’s OAM in AB effect.In this paper[2],we found an interesting role of thh electron’s OAM,namely,the AB phaseΦis related to the OAM called the“potential OAM”L potzintroduced in the recent proton spin problem[3]throughthe relation:Φ=e ∫d x·A⊥(x)=2πL potz,L potz≡e(x×A⊥)z,(2)where A⊥is the transverse component of the gaugefield and it is known as the gauge invariant quantity.The above expression clearly indicates the close relation between the electron’s potential OAM L potzand the observable in the AB effect,i.e.AB phaseΦ.It is notable that the above relation was not written in literaturesand wefirst pointed out the importance of the role of potential OAM L potzin AB effect[2].We will continue our research of the physics related to the nucleon spin/OAM and the research of AB effect.References[1]Y.Aharonov,D.Bohm,Phys.Rev,115(1959)485.[2]M.Wakamatsu,Y.Kitadono,L.P.Zou,et al.,Ann.Phys,397(2018)259.。

The update to version 15.94 incorporates the following changes:
15.94版本更新包含以下内容：
Features:
新增功能：
1. A new feature, QUANTIZE, will round off thickness or airspaces to a
given decimal precision, for users who want round numbers on their
drawings.
新增功能QUANTIZE，将厚度或空气间隔四舍五入到给定的小数精度。

以满足用户在绘图时的需要。

Bugs Fixed:
漏洞修复：
1. The blaze height of a DOE was not listed correctly if the DOE was on
side 2 of the element.
修复了如果DOE位于元件的第二个面时，则不能正确列出DOE的闪耀高度的漏洞。

2. The listing of switches on the MOM dialog was incorrect for switch 12.
修复了MOM对话框中的开关列表对于开关12不正确的漏洞。

3. The algorithm for finding the intersection of a ray with an aspheric
surface did not work if the lens was much smaller than one mm in diameter.
修复了如果透镜直径远小于1mm时，则寻找光线与非球面相交的算法不能工作的漏洞。

The update to version 15.98 incorporates the following changes:15.98版本更新包含以下内容：Features:新增功能：1. ARGLASS now accepts an argument NRM, which will defeat the errormessage that is shown when the index range of a material does notcover that in the lens. Normally this is a good check, but whenmatching plastics with the U catalog, if the range is only slightly out, the error is of no concern — and is displayed by every core in multicoremode, which is not friendly.ARGLASS现在接受一个参数NRM，当材料的折射率范围不包括镜头中的折射率范围时，该参数将消除显示的错误消息。

通常这是一个很好的检查，但当使用U目录匹配塑料时，如果范围只是稍微超出，错误是没有关系的-并显示多核模式下每个核心，这是不友好的。

2. The MRG dialog now has a button to include the NRM argument in theMACro that gets run.MRG对话框现在有一个按钮，可以在运行的宏中包含NRM参数。

Bugs Fixed:1. ZSEARCH did not get the final lens back if running in only CORE 0.修复了如果仅在CORE 0上运行，那么ZSEARCH不能得到返回的最终镜头的漏洞。