第4章
This commit is contained in:
veypi
parent
48b76c2e72
commit
206f1e236c
13
Makefile
13
Makefile
@ -5,13 +5,24 @@
|
||||
# Distributed under terms of the Apache license.
|
||||
#
|
||||
|
||||
pdf:
|
||||
pdf2:
|
||||
@rm ./build/main.pdf
|
||||
@xelatex -output-directory=./build/ main.tex
|
||||
# @zathura ./build/main.pdf
|
||||
@open ./build/main.pdf
|
||||
|
||||
pdf:
|
||||
xelatex main.tex
|
||||
-bibtex main.aux
|
||||
xelatex main.tex
|
||||
xelatex main.tex
|
||||
|
||||
show: pdf
|
||||
@open main.pdf
|
||||
|
||||
|
||||
clean:
|
||||
@find . -name '*.aux' -print0 | xargs -0 rm -rf
|
||||
@rm main.pdf
|
||||
@rm -rf *.lof *.log *.lot *.out *.toc *.bbl *.blg *.thm
|
||||
|
||||
|
||||
353
data/bibs.bib
353
data/bibs.bib
@ -1,240 +1,167 @@
|
||||
This file was created with JabRef 2.1 beta 2.
|
||||
Encoding: GB2312
|
||||
|
||||
@book{kottwitz2011latex,
|
||||
title={LaTeX Beginner's Guide},
|
||||
author={Kottwitz, S.},
|
||||
isbn={9781847199867},
|
||||
url={http://books.google.com.hk/books?id=rB1Cb62dVnUC},
|
||||
@inproceedings{2012The,
|
||||
title={The Digital Twin Paradigm for Future NASA and U.S. Air Force Vehicles},
|
||||
author={ Glaessgen, E. and Stargel, D. },
|
||||
booktitle={Aiaa/asme/asce/ahs/asc Structures, Structural Dynamics ; Materials Conference Aiaa/asme/ahs Adaptive Structures Conference Aiaa},
|
||||
year={2012},
|
||||
abstract={Future generations of NASA and U.S. Air Force vehicles will require lighter mass while being subjected to higher loads and more extreme service conditions over longer time periods than the present generation. Current approaches for certification, fleet management and sustainment are largely based on statistical distributions of material properties, heuristic design philosophies, physical testing and assumed similitude between testing and operational conditions and will likely be unable to address these extreme requirements. To address the shortcomings of conventional approaches, a fundamental paradigm shift is needed. This paradigm shift, the Digital Twin, integrates ultra-high fidelity simulation with the vehicle's on-board integrated vehicle health management system, maintenance history and all available historical and fleet data to mirror the life of its flying twin and enable unprecedented levels of safety and reliability.},
|
||||
}
|
||||
|
||||
@article{2011Reengineering,
|
||||
title={Reengineering Aircraft Structural Life Prediction Using a Digital Twin},
|
||||
author={ Tuegel, E. J. and Ingraffea, A. R. and Eason, T. G. and Spottswood, S. M. },
|
||||
journal={International Journal of Aerospace Engineering},
|
||||
volume={2011},
|
||||
number={1687-5966},
|
||||
year={2011},
|
||||
publisher={Packt Publishing}
|
||||
abstract={Reengineering of the aircraft structural life prediction process to fully exploit advances in very high performance digital computing is proposed. The proposed process utilizes an ultrahigh fidelity model of individual aircraft by tail number, a Digital Twin, to integrate computation of structural deflections and temperatures in response to flight conditions, with resulting local damage and material state evolution. A conceptual model of how the Digital Twin can be used for predicting the life of aircraft structure and assuring its structural integrity is presented. The technical challenges to developing and deploying a Digital Twin are discussed in detail.},
|
||||
}
|
||||
|
||||
@ARTICLE{idlemem,
|
||||
author = {A. Acharya and S. Setia},
|
||||
title = {Availability and Utility of Idle Memory in Workstation Clusters},
|
||||
journal = {ACM SIGMETRICS Performance Evaluation Review},
|
||||
year = {1999}
|
||||
}
|
||||
%期刊文章
|
||||
|
||||
@TECHREPORT{sigsegv,
|
||||
author = {E. A. Anderson and J. M. Neefe},
|
||||
title = {An Exploration of Network RAM},
|
||||
institution = {UC Berkley},
|
||||
year = {1994},
|
||||
number = {CSD-98-1000},
|
||||
month = dec
|
||||
}
|
||||
%技术报告？
|
||||
|
||||
@ARTICLE{Myrinet,
|
||||
author = {N.J. Boden and D. Cohen and R.E. Felderman and A.E. Kulawik and C.
|
||||
L. Seitz and J.N. Seizovic and W. Su},
|
||||
title = {Myrinet: A Gigabit-per-Second Local Area Network},
|
||||
journal = {IEEE Micro},
|
||||
year = {1995},
|
||||
volume = {15},
|
||||
pages = {29--36},
|
||||
number = {1}
|
||||
}
|
||||
%期刊文章
|
||||
|
||||
@BOOK{ulk3rd,
|
||||
title = {Understanding the Linux Kernel},
|
||||
publisher = {O'{\MakeUppercase{R}}eilly},
|
||||
year = {2005},
|
||||
author = {Daniel P. Bovet and Marco Cesati},
|
||||
edition = {3rd},
|
||||
booktitle = {Understanding the Linux Kernel},
|
||||
isbn = {0-596-00565-2}
|
||||
}
|
||||
%书籍
|
||||
|
||||
@BOOK{ldd3rd,
|
||||
title = {Linux Device Drivers},
|
||||
publisher = {O'{\MakeUppercase{R}}eilly},
|
||||
year = {2005},
|
||||
author = {Jonathan Corbet and Alessandro Rubini and Greg Kroah-Hartman},
|
||||
edition = {3rd},
|
||||
booktitle = {Linux Device Drivers}
|
||||
}
|
||||
%书籍
|
||||
|
||||
@ARTICLE{GMM,
|
||||
author = {M. J. Feeley and W. E. Morgan and F. H. Pighin and A. R. Karlin and
|
||||
H. M. Levy and C. A. Thekkath},
|
||||
title = {Implementing Global Memory Management in a Workstation Cluster},
|
||||
journal = {ACM SIGOPS Operating Systems Review},
|
||||
year = {1995},
|
||||
pages = {201--212}
|
||||
}
|
||||
%期刊文章
|
||||
|
||||
@ARTICLE{nrd,
|
||||
author = {M. D. Flouris and E. P. Markatos},
|
||||
title = {The Network RamDisk: Using Remote Memory on Heterogeneous NOWs},
|
||||
journal = {Cluster Computing},
|
||||
year = {1999},
|
||||
volume = {2},
|
||||
pages = {281--293},
|
||||
number = {4}
|
||||
}
|
||||
%期刊文章
|
||||
|
||||
@INPROCEEDINGS{1992GMM,
|
||||
author = {M. J. Frankling and M. J. Carey and M. Livny},
|
||||
title = {Globla memory management in client-server DBMS architectures},
|
||||
booktitle = {Proceeding of the 18th VLDB Conference},
|
||||
year = {1992},
|
||||
month = aug
|
||||
}
|
||||
%会议论文？
|
||||
|
||||
@INPROCEEDINGS{iSCSIIOprof,
|
||||
author = {Jizhong Han and Dan Zhou and Xubin He and Jinzhu Gao},
|
||||
title = {I/{\MakeUppercase{O}} Profiling for Distributed IP Storage Systems},
|
||||
booktitle = {Proceeding of The Second International Conference on Embedded Software
|
||||
and Systems},
|
||||
year = {2005},
|
||||
month = dec
|
||||
@article{2017Digital,
|
||||
title={Digital Twin: Mitigating Unpredictable, Undesirable Emergent Behavior in Complex Systems},
|
||||
author={ Grieves, M. and Vickers, J. },
|
||||
journal={Springer International Publishing},
|
||||
year={2017},
|
||||
abstract={Systems do not simply pop into existence. They progress through lifecycle phases of creation, production, operations, and disposal. The issues leading to undesirable and unpredicted emergent behavior are set in place during the phases of creation and production and realized during the operational phase, with many of those problematic issues due to human interaction. We propose that the idea of the Digital Twin, which links the physical system with its virtual equivalent can mitigate these problematic issues. We describe the Digital Twin concept and its development, show how it applies across the product lifecycle in defining and understanding system behavior, and define tests to evaluate how we are progressing. We discuss how the Digital Twin relates to Systems Engineering and how it can address the human interactions that lead to "normal accidents." We address both Digital Twin obstacles and opportunities, such as system replication and front running. We finish with NASA's current work with the Digital Twin.},
|
||||
}
|
||||
|
||||
@INPROCEEDINGS{icache1,
|
||||
author = {X. He and Q. Yang and M. Zhang},
|
||||
title = {A Caching Strategy to Improve iSCSI Performance},
|
||||
booktitle = {Proceeding of Local Computer Networks},
|
||||
year = {2002}
|
||||
@article{2020Integration,
|
||||
title={Integration of Digital Twin and Deep Learning in Cyber-Physical Systems: Towards Smart Manufacturing},
|
||||
author={ Lee, J. },
|
||||
volume={38},
|
||||
number={8},
|
||||
pages={901-910},
|
||||
year={2020},
|
||||
abstract={No abstract available.},
|
||||
}
|
||||
|
||||
@MASTERSTHESIS{NFS,
|
||||
author = {M. R. Hines and M. Lewandowski and K. Gopalan},
|
||||
title = {Anemone: Adaptive Network Memory Engine},
|
||||
school = {Florida State University},
|
||||
year = {2003}
|
||||
}
|
||||
%硕士论文
|
||||
|
||||
@INPROCEEDINGS{memserver,
|
||||
author = {L. Iftode and K. Li and K. Petersen},
|
||||
title = {Memory Servers for Multicomputers},
|
||||
booktitle = {Proceeding of the IEEE Spring COMPCON 93},
|
||||
year = {1993},
|
||||
pages = {538-547},
|
||||
month = feb
|
||||
@article{2017The,
|
||||
title={The Digital Twin: Realizing the Cyber-Physical Production System for Industry 4.0},
|
||||
author={ Uhlemann, H. J. and Lehmann, C. and Steinhilper, R. },
|
||||
journal={Procedia CIRP},
|
||||
volume={61},
|
||||
pages={335-340},
|
||||
year={2017},
|
||||
abstract={Concerning current approaches to planning of manufacturing processes, the acquisition of a sufficient data basis of the relevant process information and subsequent development of feasible layout options requires 74% of the overall time-consumption. However, the application of fully automated techniques within planning processes is not yet common practice. Deficits are to be observed in the course of the use of a fully automated data acquisition of the underlying process data, a key element of Industry 4.0, as well as the evaluation and quantification and analysis of the gathered data. As the majority of the planning operations are conducted manually, the lack of any theoretical evaluation renders a benchmarking of the results difficult. Current planning processes analyze the manually achieved results with the aid of simulation. Evaluation and quantification of the planning procedure are limited by complexity that defies manual controllability. Research is therefore required with regard to automated data acquisition and selection, as the near real-time evaluation and analysis of a highly complex production systems relies on a real-time generated database. The paper presents practically feasible approaches to a multi-modal data acquisition approach, its requirements and limitations. The further concept of the Digital Twin for a production process enables a coupling of the production system with its digital equivalent as a base for an optimization with a minimized delay between the time of data acquisition and the creation of the Digital Twin. Therefore a digital data acquisition approach is necessary. As a consequence a cyber-physical production system can be generated, that opens up powerful applications. To ensure a maximum concordance of the cyber-physical process with its real-life model a multimodal data acquisition and evaluation has to be conducted. The paper therefore presents a concept for the composition of a database and proposes guidelines for the implementation of the Digital Twin in production systems in small and medium-sized enterprises.},
|
||||
}
|
||||
|
||||
@INPROCEEDINGS{dodo,
|
||||
author = {S. Koussih and A. Acharyam, S. Setia},
|
||||
title = {Dodo:A User-level System for Exploiting Idle Memory in Workstation
|
||||
Clusters},
|
||||
booktitle = {Proceeding of the Eighth IEEE International Symposium on High Performance
|
||||
Distributed Computing},
|
||||
year = {1999}
|
||||
@article{2017C2PS,
|
||||
title={C2PS: A Digital Twin Architecture Reference Model for the Cloud-Based Cyber-Physical Systems},
|
||||
author={ Alam, K. M. and Saddik, A El },
|
||||
journal={IEEE Access},
|
||||
volume={5},
|
||||
pages={2050-2062},
|
||||
year={2017},
|
||||
abstract={Cyber-physical system (CPS) is a new trend in the Internet-of-Things related research works, where physical systems act as the sensors to collect real-world information and communicate them to the computation modules (i.e. cyber layer), which further analyze and notify the findings to the corresponding physical systems through a feedback loop. Contemporary researchers recommend integrating cloud technologies in the CPS cyber layer to ensure the scalability of storage, computation, and cross domain communication capabilities. Though there exist a few descriptive models of the cloud-based CPS architecture, it is important to analytically describe the key CPS properties: computation, control, and communication. In this paper, we present a digital twin architecture reference model for the cloud-based CPS, C2PS, where we analytically describe the key properties of the C2PS. The model helps in identifying various degrees of basic and hybrid computation-interaction modes in this paradigm. We have designed C2PS smart interaction controller using a Bayesian belief network, so that the system dynamically considers current contexts. The composition of fuzzy rule base with the Bayes network further enables the system with reconfiguration capability. We also describe analytically, how C2PS subsystem communications can generate even more complex system-of-systems. Later, we present a telematics-based prototype driving assistance application for the vehicular domain of C2PS, VCPS, to demonstrate the efficacy of the architecture reference model.},
|
||||
}
|
||||
|
||||
@ARTICLE{HPBD,
|
||||
author = {S. Liang and R. Notonha and D. K. Panda},
|
||||
title = {Swapping to Remote Memory over InfiniBand: An Approach using a High
|
||||
Performance Network Block Device},
|
||||
journal = {IEEE Cluster Computing},
|
||||
year = {2005},
|
||||
month = sep
|
||||
}
|
||||
%期刊文章
|
||||
|
||||
@BOOK{lkd2nd,
|
||||
title = {Linux Kernel Development},
|
||||
publisher = {Sams Publishing},
|
||||
year = {2005},
|
||||
author = {Robert Love},
|
||||
edition = {2nd},
|
||||
booktitle = {Linux Kernel Development},
|
||||
isbn = {0-672-32720-1}
|
||||
}
|
||||
%书籍
|
||||
|
||||
@INPROCEEDINGS{rrmp,
|
||||
author = {E. P. Markatos and G. Dramitions},
|
||||
title = {Implementation of a Reliable Remote Memory Pager},
|
||||
booktitle = {Proceeding of the 1996 Usenix Technical Conference},
|
||||
year = {1996}
|
||||
@inproceedings{2005Digital,
|
||||
title={Digital Twin Spark Ignition for Improved Fuel Economy and Emissions on Four Stroke Engines},
|
||||
author={ Ramtilak, A. and Joseph, A. and Sivakumar, G. and Bhat, S. S. },
|
||||
booktitle={SIAT 2005},
|
||||
year={2005},
|
||||
abstract={The Digital Twin Spark Ignition (DTS-i) is a concept developed specifically for small bore four stroke engines with two valves. Two spark plugs placed diametrically opposite to each other in the combustion chamber fire simultaneously igniting the charge. The benefit of this concept is improved fuel economy, better drivability, and reduced engine on a emissions. The concept has been successfully launched on two products namely 150 DTS-i and 180 DTS-i engine. The DTS-i concept helps the products meet the India 2005-emission standard without the use of secondary air injection and exhaust after treatment.},
|
||||
}
|
||||
|
||||
@OTHER{stream,
|
||||
author = {John McCalpin},
|
||||
etype = {CP},
|
||||
howpublished = {http://www.streambench.org},
|
||||
title = {Streambenchmark},
|
||||
url = {http://www.streambench.org}
|
||||
}
|
||||
%其他
|
||||
|
||||
@INPROCEEDINGS{Nswap,
|
||||
author = {T. Newhall and S. Finney and K. Ganchevm and M. Spiegel},
|
||||
title = {Nswap:A Network Swapping Module for Linux Clusters},
|
||||
booktitle = {Proceeding of Euro-Par'03 International Conference on Parallel and
|
||||
Distributed Computing},
|
||||
year = {2003},
|
||||
address = {Klagenfurt, Austria},
|
||||
month = aug
|
||||
@article{2014On,
|
||||
title={On the Effects of Modeling As-Manufactured Geometry: Toward Digital Twin},
|
||||
author={ Cerrone, A and Hochhalter, J and Heber, G and Ingraffea, A },
|
||||
journal={International Journal of Aerospace Engineering},
|
||||
volume={2014},
|
||||
year={2014},
|
||||
abstract={A simple, nonstandardized material test specimen, which fails along one of two different likely crack paths, is considered herein. The result of deviations in geometry on the order of tenths of a millimeter, this ambiguity in crack path motivates the consideration of as-manufactured component geometry in the design, assessment, and certification of structural systems. Herein, finite element models of as-manufactured specimens are generated and subsequently analyzed to resolve the crack-path ambiguity. The consequence and benefit of such a ???personalized??? methodology is the prediction of a crack path for each specimen based on its as-manufactured geometry, rather than a distribution of possible specimen geometries or nominal geometry. The consideration of as-manufactured characteristics is central to the Digital Twin concept. Therefore, this work is also intended to motivate its development.},
|
||||
}
|
||||
|
||||
@INPROCEEDINGS{manager,
|
||||
author = {J. Oleszkiewicz and L. Xiao and Y. Liu},
|
||||
title = {Parallel Network RAM: Effectively Utilizing Global Cluster memory
|
||||
for Large Data-Intensive Parallel Programs},
|
||||
booktitle = {Proceeding of International Conference on Parallel Proceeding},
|
||||
year = {2004},
|
||||
pages = {577-592}
|
||||
@article{2018Digital,
|
||||
title={Digital Twin and Big Data Towards Smart Manufacturing and Industry 4.0: 360 Degree Comparison},
|
||||
author={ Qi, Q. and Tao, F. },
|
||||
journal={IEEE Access},
|
||||
pages={3585-3593},
|
||||
year={2018},
|
||||
abstract={With the advances in new-generation information technologies, especially big data and digital twin, smart manufacturing is becoming the focus of global manufacturing transformation and upgrading. Intelligence comes from data. Integrated analysis for the manufacturing big data is beneficial to all aspects of manufacturing. Besides, the digital twin paves a way for the cyber-physical integration of manufacturing, which is an important bottleneck to achieve smart manufacturing. In this paper, the big data and digital twin in manufacturing are reviewed, including their concept as well as their applications in product design, production planning, manufacturing, and predictive maintenance. On this basis, the similarities and differences between big data and digital twin are compared from the general and data perspectives. Since the big data and digital twin can be complementary, how they can be integrated to promote smart manufacturing are discussed.},
|
||||
}
|
||||
|
||||
@ARTICLE{Quadrics,
|
||||
author = {Fabrizio Petrini and Eitan Frachtenberg and Adolfy Hoisie and Salvador
|
||||
Coll},
|
||||
title = {Performance Evaluation of the Quadrics Interconnection Network},
|
||||
journal = {Journal of Cluster Computing},
|
||||
year = {2003},
|
||||
volume = {6},
|
||||
pages = {125--142},
|
||||
number = {2},
|
||||
month = apr
|
||||
}
|
||||
%期刊文章
|
||||
|
||||
@INPROCEEDINGS{NBD,
|
||||
author = {Sun, H. Tang and M. Chen and J. Fan},
|
||||
title = {A Scalable Dynamic Network Memory Service System},
|
||||
booktitle = {Proceeding of High-Performance Computing in Asia-Pacific Region},
|
||||
year = {2005}
|
||||
@article{Anwer2017Shaping,
|
||||
title={Shaping the digital twin for design and production engineering},
|
||||
author={Anwer and Nabil and Schleich and Benjamin and Mathieu and Luc and Wartzack and Sandro},
|
||||
journal={CIRP Annals},
|
||||
year={2017},
|
||||
abstract={The digitalization of manufacturing fuels the appl},
|
||||
}
|
||||
|
||||
@INPROCEEDINGS{VMA,
|
||||
author = {T. S. Trevisan and V. S. Costal and L. Whately and C. L. Amorim},
|
||||
title = {Distributed Shared Memory in Kernel Mode},
|
||||
booktitle = {Proceeding of Computer Architecture and High Performance Computing},
|
||||
year = {2002}
|
||||
@article{陶飞2017Digital,
|
||||
title={Digital twin workshop:a new paradigm for future workshop},
|
||||
author={陶飞 and 张萌 and 程江峰 and 戚庆林},
|
||||
journal={Computer Integrated Manufacturing Systems},
|
||||
volume={23},
|
||||
number={第1期},
|
||||
year={2017},
|
||||
abstract={With the integration and extensive applications for new generation of information technologies(such as cloud computing,internet of things,big data,mobile internet,artificial intelligence)in manufacturing industry,a number of countries had put forward their national advanced manufacturing development strategies,such as Industry4.0in Germany,Industrial Internet and manufacturing system based on Cyber-Physical Systems(CPS)in USA,as well as Made in China 2025 and Internet Plus Manufacturing in China.Although each of these strategies was proposed under different circumstances,one of the common purposes of these strategies was to achieve the interconnection,interoperability between physical world and the information world of manufacturing and the intelligent operation of manufacturing.As one of bottlenecks to achieve this purpose,the communication and interaction between the physical world and the information world of manufacturing must be solved.To solve the problem,a novel concept of Digital Twin Workshop(DTW)based on digital twin was proposed.Complementary to the concept,the characteristics,architecture,system composition,operating mechanism and enabling key technologies were also elaborated and discussed respectively.On this basis,the theory and implementation of the communication and interaction between physical and information world of workshop based on workshop digital twin data were discussed.},
|
||||
}
|
||||
|
||||
@ARTICLE{bigmem,
|
||||
author = {L. Xiao and S. Chen and X. Zhang},
|
||||
title = {Adaptive Memory Allocations in Clusters to Handle Unexpctedly Large
|
||||
Data-Intensive Jobs},
|
||||
journal = {IEEE Transactions on Parallel and Distributed Systems},
|
||||
year = {2004},
|
||||
volume = {15},
|
||||
pages = {577-592},
|
||||
number = {6},
|
||||
month = jun
|
||||
@inproceedings{2017Generating,
|
||||
title={Generating Digital Twin Models using Knowledge Graphs for Industrial Production Lines},
|
||||
author={ Banerjee, A. and Dalal, R. and Mittal, S. and Joshi, K. P. },
|
||||
booktitle={9th ACM Web Science Conference, Industrial Knowledge Graphs},
|
||||
year={2017},
|
||||
abstract={Digital Twin models are computerized clones of physical assets that can be used for in-depth analysis. Industrial production lines tend to have multiple sensors to generate near real-time status information for production. Industrial Internet of Things datasets are difficult to analyze and infer valuable insights such as points of failure, estimated overhead. etc. In this paper we introduce a simple way of formalizing knowledge as digital twin models coming from sensors in industrial production lines. We present a way on to extract and infer knowledge from large scale production line data, and enhance manufacturing process management with reasoning capabilities, by introducing a semantic query mechanism. Our system primarily utilizes a graph-based query language equivalent to conjunctive queries and has been enriched with inference rules.},
|
||||
}
|
||||
%期刊文章
|
||||
|
||||
@OTHER{IB,
|
||||
etype = {OL},
|
||||
howpublished = {http://www.infinibandta.org/spec},
|
||||
key = {ITA},
|
||||
organization = {InfiniBand Trade Association},
|
||||
title = {The InfiniBand Architecture},
|
||||
url = {http://www.infinibandta.org/spec}
|
||||
@article{Wagner2017The,
|
||||
title={The role of the Industry 4.0 Asset Administration Shell and the Digital Twin during the life cycle of a plant},
|
||||
author={Wagner and C and Grothoff and J and Epple and U and Drath and R and Malakuti and S},
|
||||
journal={IEEE Int C Emerg},
|
||||
year={2017},
|
||||
abstract={Industry 4.0 has come up with an impressive number of additional terms and definitions e.g. Asset Administration Shell or Digital Twin. Those terms stand for Industry 4.0 core paradigms, but their meaning is not harmonized even among experts. This is a source of misunderstanding and confusion. In this paper, the mentioned terms are discussed along the life cycle of a plant. A plant's life cycle comprises the whole process from its idea to its destruction. During the discussion of the terms not only the concepts, but also the visions of Industry 4.0 are clarified. Goal of this paper is not to define additional terms, but to explain and substantiate existing ones and to solve apparent contradictions. Additional outcome of the discussion are architectural recommendations for an upcoming Industry 4.0 architecture. Moreover, suggestions for device manufacturers, system integrators, plant owners and Industry 4.0 architects are given.},
|
||||
}
|
||||
%其他
|
||||
|
||||
@article{韩辉2019Digital,
|
||||
title={Digital Twin Service towards Smart Manufacturing},
|
||||
author={韩辉},
|
||||
journal={疾病监测},
|
||||
year={2019},
|
||||
abstract={<span style="font-family: 宋体;">参考译名:面向智能制造的</span><span style="background: white; color: rgb(51, 51, 51); font-family:;">"</span><span style="background: white; color: rgb(51, 51, 51); font-family: 宋体;">数字双胞胎</span><span style="background: white; color: rgb(51, 51, 51); font-family:;">"</span><span style="background: white; color: rgb(51, 51, 51); font-family: 宋体;">(</span><span style="background: white; color: rgb(51, 51, 51); font-family:;">Digital Twin</span><span style="background: white; color: rgb(51, 51, 51); font-family: 宋体;">)</span><span style="font-family: Calibri;">服务</span><span style="font-family: 宋体;"></span><span style="font-family: Calibri;">Digital twin provides an effective way for the cyber-physical integration of manufacturing. Meanwhile, smart manufacturing services could optimize the entire business processes and operation procedure of manufacturing, to achieve a new higher level of productivity. The combination of smart manufacturing services and digital twin would radically change product design, manufacturing, usage, MRO and other processes. Combined with the services, the digital twin will generate more reasonable manufacturing planning and precise production control to help achieve smart manufacturing, through the two-way connectivity between the virtual and physical worlds of manufacturing. This paper specifies and highlights how manufacturing services and digital twin are converged together and the various components of digital twin are used by manufacturers in the form of services.</span><span style="font-family: 宋体;">来源:【刊名】:</span><span style="font-family: Calibri;">Procedia CIRP</span><span style="font-family: 宋体;">【</span><span style="font-family: Calibri;">ISSN</span><span style="font-family: 宋体;">】:</span><span style="font-family: Calibri;">2212-8271</span><span style="font-family: 宋体;">【出版信息】:</span><span style="font-family: Calibri;">2018 Vol.72</span>},
|
||||
}
|
||||
|
||||
@article{2022Validation,
|
||||
title={Validation of materials-informed digital twin: Mapping residual strains in HSLA steel weldment using high energy X-rays},
|
||||
author={ Fisher, Charles R. and Nygren, Kelly E. and Beaudoin, Armand J. },
|
||||
journal={Journal of manufacturing processes},
|
||||
number={74-Feb.},
|
||||
year={2022},
|
||||
}
|
||||
|
||||
@article{2021SARS,
|
||||
title={SARS-CoV-2 Spread Forecast Dynamic Model Validation Thorough Digital Twin Approach, Catalonia Case Study},
|
||||
author={ Pau, Fic and Joan, Gis and GIC V铆Ctor and XP I Palom茅S},
|
||||
year={2021},
|
||||
}
|
||||
|
||||
@article{2021Research,
|
||||
title={Research on Digital Twin Framework of Military Large-scale UAV Based on Cloud Computing},
|
||||
author={ Wang, Y. C. and Zhang, N. and Li, H. and Cao, J. },
|
||||
journal={Journal of Physics: Conference Series},
|
||||
volume={1738},
|
||||
number={1},
|
||||
pages={012052 (6pp)},
|
||||
year={2021},
|
||||
abstract={Firstly, this article explains the characteristics and advantages of military large-scale UAVs, and points out the three basic problems currently encountered by military large-scale UAVs; secondly, this article is based on the current design, manufacturing and application reality of large-scale military UAVs, analyzed the urgent need to build a cloud computing-based digital twin framework for military large-scale UAVs, and discussed in detail from the aspects of test cost, integrated perception, centralized control, business prediction, and mission planning; again, this article proposed cloud-based computing The digital twin framework for military large-scale UAVs discusses the composition and functions of each layer; finally, it points out the five directions and work priorities that need to be paid attention to in the construction of the digital twin system of military large-scale UAVs, including UAV model, flight status measurement, reliable propagation channel, intelligent command and control, and capability evaluation analysis.},
|
||||
}
|
||||
|
||||
@article{2021Intelligent,
|
||||
title={Intelligent Ironmaking Optimization Service on a Cloud Computing Platform by Digital Twin - ScienceDirect},
|
||||
author={ Zhou, H. and Yang, C. and Sun, Y. },
|
||||
journal={工程(英文)},
|
||||
year={2021},
|
||||
abstract={The shortage of computation methods and storage devices has largely limited the development of multiobjective optimization in industrial processes.To improve the operational levels of the process industries,we propose a multi-objective optimization framework based on cloud services and a cloud distribution system.Real-time data from manufacturing procedures are first temporarily stored in a local database,and then transferred to the relational database in the cloud.Next,a distribution system with elastic compute power is set up for the optimization framework.Finally,a multi-objective optimization model based on deep learning and an evolutionary algorithm is proposed to optimize several conflicting goals of the blast furnace ironmaking process.With the application of this optimization service in a cloud factory,iron production was found to increase by 83.91 td^(-1),the coke ratio decreased 13.50 kgt^(-1),and the silicon content decreased by an average of 0.047%.},
|
||||
}
|
||||
|
||||
@misc{2021PRECISION,
|
||||
title={PRECISION TREATMENT WITH MACHINE LEARNING AND DIGITAL TWIN TECHNOLOGY FOR OPTIMAL METABOLIC OUTCOMES},
|
||||
author={ Hadley, F. and Dunlap, T. A. and Poon, Tcy },
|
||||
year={2021},
|
||||
abstract={A patient health management platform accesses a metabolic profile for a patient and biosignals recorded for the patient during a current time period comprising sensor data and/or lab test data collected for the patient. The platform encodes the biosignals into a vector representation and inputs the vector representation into a patient-specific metabolic model to determine a metabolic state of the patient at a conclusion of the current time period. The patient-specific metabolic model comprises a set of parameter values determined based on labels assigned to the previous metabolic states and a function representing one or more effects of the plurality of biosignals of the personalized metabolic profile. The platform compares the determined metabolic state of the patient to a threshold metabolic state representing a target metabolism. The platform generates a patient-specific treatment recommendation outlining instructions for the patient to improve the determined metabolic state to the functional metabolic state.},
|
||||
}
|
||||
|
||||
|
||||
@ -1,82 +1,33 @@
|
||||
% !Mode:: "TeX:UTF-8"
|
||||
\chapter{简介}
|
||||
\chapter{数字孪生}
|
||||
|
||||
\section{项目说明}
|
||||
\section{概述}
|
||||
|
||||
欢迎使用北京航空航天大学毕业设计论文毕业设计论文\LaTeX{}模板，
|
||||
本模板由北航开源俱乐部(BHOSC)维护，根据北京航空航天大学教务处的
|
||||
本科生毕业设计论文要求和研究生毕业设计论文要求来编写的。
|
||||
数字产品定义(Digital product definition, DPD)经历了从二维到三维的发展。业界提出了以产品设计为核心的数字仿真(DMU)、虚拟样机等技术，产品设计信息的定义和表达也越来越完善。近年来，国内外制造业的经验表明，3D数字化定义的产品模式已经成熟，其效益被反复验证。但是，目前的数字化产品定义还存在描述不涉及制造、运行和维护阶段、产品定义和过程定义之间缺乏相关性、后续模拟基于“理想定义”对真实产品的指导有限等问题。为了解决上述问题，“数字孪生”技术应运而生。数字孪生技术被誉为有望改变未来制造“游戏规则”的顶级技术。这项技术使用数据馈送来映射物理实体，并正在对工业的许多领域产生颠覆性的影响。德国信息技术和新媒体协会预测，在制造业市场中，数字孪生的价值是巨大的，到2025年将超过780亿欧元。Gartner已经连续两年(2016、2017)将数字孪生列为十大战略技术发展趋势之一。2017年11月，世界上最大的武器制造商洛克希德･马丁公司将数字孪生列为未来国防和航空航天工业的六大顶级技术。
|
||||
|
||||
目前本模板支持本科、硕士和博士研究生毕业设计论文要求规范。
|
||||
数字孪生是真实产品的虚拟表示。它拥有产品的信息，从产品生命的开始一直到产品的处置。在网络物理系统的语境中，数字孪生可以被看作是一个网络表征，是其特征点的对象集合，其中泛函其物理机制、虚拟特征和与人的交互关系。
|
||||
|
||||
本模板在编写过程中尽可能满足学校要求，但是由于原始规范主要针对Word。
|
||||
和\LaTeX{}之间不可避免的差异加之编写者的水平限制，本模板很难做到完全一致。
|
||||
我们十分欢迎北航的\LaTeX{}爱好者/专家参与到本模板的完善工作中，
|
||||
希望本模板能够对各位同学的论文撰写工作提供便利，
|
||||
感谢您对我们工作的信任以及任何可能的反馈和贡献。
|
||||
如果您对开发和完善本模板\,BUAAthesis.cls\,有兴趣，
|
||||
或者有任何想法和建议，请与我们联系！
|
||||
在真实的实践场景中，数字孪生往往会遇到复杂的现实问题，如海量信息的建模、处理问题，模型的结构化专有化问题等等。单一场景即有可能需要构建几千孪生体并处理每秒几十万量级的数据，如何根据已有知识构建模型，如何描述模型特征和状态，如何关联、分析、响应大量数据，是本篇文章的主要研究内容。
|
||||
|
||||
{\heiti 注意：}本模板在尽可能满足学校要求的同时，在细节处理上，
|
||||
倾向于遵从\LaTeX{}排版规范，避免使用奇怪的宏包和编写者认为不规范的设置。
|
||||
所以难免和学校提供的基于Word的样张存在细微差异，请谨慎使用！
|
||||
鉴于以上生产需要，本文提出了一种实时分布式通信系统以及一种知识和事件模型化方法，解决大数据情况下实时响应和高效知识处理问题，并在自研的通用型数字孪生平台上进行验证。
|
||||
|
||||
\section{相关信息}
|
||||
|
||||
\subsection{模板维护及联系方式}
|
||||
\begin{tabular}{ll}
|
||||
\multicolumn{2}{l}{北航开源俱乐部 BeiHang OpenSource Club (BHOSC)} \\
|
||||
GoogleGroup & \url{https://groups.google.com/d/forum/BHOSC/} \\
|
||||
Github & \url{https://github.com/BHOSC/} \\
|
||||
IRC & \#beihang-osc @ FreeNode
|
||||
\end{tabular}
|
||||
|
||||
\subsection{代码托管及相关页面}
|
||||
\begin{itemize}
|
||||
\item 毕业设计论文模板代码
|
||||
\item[] \url{https://github.com/BHOSC/BUAAthesis/}
|
||||
% TODO(huxuan): Others pages related to BUAAthesis
|
||||
% \item 软件学院本科毕设答辩演示模板
|
||||
% \item[] \url{https://github.com/huxuan/latex\_buaasoft\_bachelor\_slide}
|
||||
% \item 研究生毕设综述报告和开题报告模板
|
||||
% \item[] \url{https://github.com/JosephPeng/ZongshuKaiti\}
|
||||
\end{itemize}
|
||||
\section{总体方案}
|
||||
|
||||
\subsection{贡献者}
|
||||
\begin{tabularx}{\textwidth}{@{\hspace{2em}}ll}
|
||||
\href{https://github.com/JosephPeng/}{Joseph \footnote{目前的维护者}} &
|
||||
\href{mailto:pengyongbuaa@gmail.com}{pengyongbuaa@gmail.com} \\
|
||||
\href{http://huxuan.org/}{huxuan \textsuperscript{1}} &
|
||||
\href{mailto:i@huxuan.org}{i@huxuan.org} \\
|
||||
\end{tabularx}
|
||||
数字孪生主要技术包括信息建模、信息采集同步，信息分析、智能决策等，虽然已经取得了很大发展，但是由于现在世界模型机理复杂、知识图谱建立困难以及有效数据采集分析困难等问题，限制了其实践形势。
|
||||
|
||||
\subsection{项目协议}
|
||||
本项目主要遵从以下两套协议
|
||||
\begin{itemize}
|
||||
\item \href{http://www.gnu.org/licenses/gpl.txt}
|
||||
{GNU General Public License (GPLv3)}
|
||||
\item \href{http://www.latex-project.org/lppl.txt}
|
||||
{\LaTeX{} Project Public License (LPPL)}
|
||||
\end{itemize}
|
||||
使用前请认真阅读相关协议，详情请见项目代码根目录下的 LICENSE 文件
|
||||
\subsection{通用平台设计}
|
||||
|
||||
\section{免责声明}
|
||||
本模板为编写者依据北京航空航天大学研究生院及教务处出台的
|
||||
《北京航空航天大学研究生撰写学位论文规定（2009年7月修订）》和
|
||||
《本科生毕业设计（论文）撰写规范及要求》编写而成，
|
||||
旨在方便北京航空航天大学毕业生撰写学位论文使用。
|
||||
\begin{figure}[h!]
|
||||
\centering
|
||||
\includegraphics[width=0.8\textwidth]{figure/f1.png}
|
||||
\caption{系统结构图}
|
||||
\label{fig-f1}
|
||||
\end{figure}
|
||||
|
||||
如前所述，本模板为北航开源俱乐部\LaTeX{}爱好者依据学校的要求规范编写，
|
||||
研究生院及教务处只提供毕业论文的写作规范，目前并未提供官方\LaTeX{}模板，
|
||||
也未授权第三方模板为官方模板，故此模板仅为论文规范的参考实现，
|
||||
不保证格式能完全满足审查老师要求。任何由于使用本模板而引起的论文格式等问题，
|
||||
以及造成的可能后果，均与本模板编写者无关。
|
||||
\subsection{通讯网络}
|
||||
\subsection{知识模型}
|
||||
\subsection{状态与事件模型}
|
||||
|
||||
任何组织或个人以本模板为基础进行修改、扩展而生成新模板，请严格遵守相关协议。
|
||||
由于违反协议而引起的任何纠纷争端均与本模板编写者无关。
|
||||
|
||||
\section{版本历史}
|
||||
\begin{itemize}
|
||||
\item[1.0] 2012/07/24 已完成大体功能，说明文档和细节方面还有待完善。
|
||||
% “a.b”为版本号，b为奇数时为内测版本，为偶数时为发行版。
|
||||
\end{itemize}
|
||||
|
||||
13
data/chapter2.tex
Normal file
13
data/chapter2.tex
Normal file
@ -0,0 +1,13 @@
|
||||
\chapter{平台设计}
|
||||
|
||||
\section{整体架构}
|
||||
|
||||
\section{功能设计}
|
||||
|
||||
\section{sql设计}
|
||||
|
||||
\section{后端设计}
|
||||
|
||||
\section{前端设计}
|
||||
|
||||
\section{交互逻辑}
|
||||
107
data/chapter3.tex
Normal file
107
data/chapter3.tex
Normal file
@ -0,0 +1,107 @@
|
||||
|
||||
\chapter{通讯网络}
|
||||
|
||||
\section{通讯拓扑}
|
||||
\begin{figure}[h!]
|
||||
\centering
|
||||
\includegraphics[width=0.8\textwidth]{figure/f3.png}
|
||||
\caption{通讯网络}
|
||||
\label{fig-f3}
|
||||
\end{figure}
|
||||
|
||||
\section{通讯协议}
|
||||
|
||||
\begin{table}
|
||||
\centering
|
||||
\caption{通讯帧}
|
||||
\begin{tabular}{|l|l|l|l|l|l|l|l|}
|
||||
\hline
|
||||
\multicolumn{4}{|c|}{prefix} & \multicolumn{4}{c|}{count} \\
|
||||
\hline
|
||||
typ & \multicolumn{3}{c|}{tag} & \multicolumn{4}{c|}{source} \\
|
||||
\hline
|
||||
\multicolumn{4}{|c|}{target} & \multicolumn{4}{c|}{data} \\
|
||||
\hline
|
||||
\multicolumn{8}{|c|}{data} \\
|
||||
\multicolumn{8}{|c|}{....} \\
|
||||
\multicolumn{8}{|c|}{data} \\
|
||||
\hline
|
||||
\end{tabular}
|
||||
\label{tab-col}
|
||||
\end{table}
|
||||
|
||||
\begin{itemize}
|
||||
\item prefix(8bit)
|
||||
\item count(8bit)
|
||||
\item typ(4bit)
|
||||
\item tag(4bit)
|
||||
\item source(8bit)
|
||||
\item target(8bit)
|
||||
\item data
|
||||
\end{itemize}
|
||||
|
||||
\section{路由算法}
|
||||
|
||||
rie树又被称为前缀树、字典树是一种用于快速检索的多叉树结构。字典树把字符串看成字符序列，根据字符串中字符序列的先后顺序构造从上到下的树结构，树结构中的每一条边都对应着一个字符。字典树上存储的字符串被视为从根节点到某个节点之间的一条路径，并在终点节点上做个标记"该节点对应词语的结尾"，正因为有终点节点的存在，字典树不仅可以实现简单的存储字符串，还可以实现字符串的映射，只需要将相对应的值悬挂在终点节点上即可。
|
||||
|
||||
Trie的核心思想是空间换时间，有如下基本性质：
|
||||
\begin{itemize}
|
||||
\item - 根节点不包含字符，除根节点外每一个节点都只包含一个字符
|
||||
\item - 从根节点到某一节点，路径上经过的字符连接起来，为该节点对应的字符串
|
||||
\item - 每个节点的所有子节点包含的字符都不相同
|
||||
\end{itemize}
|
||||
|
||||
字典树能够利用字符串中的公共前缀，这样可能会节省内存，利用字符串的公共前缀可以减少查询字符串的时间，能够最大限度的减少无谓的字符串比较，同时在查询的过程中不需要预知待查询字符串的长度，沿着字典树的边进行匹配，查询效率比较高。
|
||||
|
||||
|
||||
\section{分布式选举协议}
|
||||
\begin{figure}[h!]
|
||||
\centering
|
||||
\includegraphics[width=0.8\textwidth]{figure/f2.png}
|
||||
\caption{选举协议}
|
||||
\label{fig-f2}
|
||||
\end{figure}
|
||||
|
||||
分布式协议中，一个节点任一时刻处于以下三个状态之一：
|
||||
|
||||
\begin{itemize}
|
||||
\item 从动
|
||||
\item 候选者
|
||||
\item 主控
|
||||
\end{itemize}
|
||||
|
||||
如上图所示，可以看出所有节点启动时都是从动状态；在一段时间内如果没有收到来自主控的心跳，从从动切换到候选者，发起选举；如果收到大多数的同意票（含自己的一票）则切换到主控状态；如果发现其他节点比自己更新，则主动切换到从动。
|
||||
|
||||
总之，系统中最多只有一个主控节点，如果在一段时间里发现没有主控，则大家通过选举-投票选出主控。主控会不停的给从动发心跳消息，表明自己的存活状态。如果主控节点故障，那么从动节点会转换成候选状态，重新选出主控。
|
||||
|
||||
|
||||
\section{硬实时通信}
|
||||
|
||||
在工业控制领域实时(Real Time)是一个核心要求。实时系统是指计算的正确性不仅依赖于逻辑的正确性而且依赖于产生结果的时间，如果系统的时间限制不能得到满足，系统将会产生故障。在工业领域这种故障可能造成灾难性的结果。
|
||||
|
||||
在CPU资源调度方面，OS主要提供一个多任务(multitasking)的运行环境，以方便应用的开发。在开发某个应用时首先把工作拆解成多个任务(Task/Thread)，每个任务都可以简化成一个简单的无限循环：
|
||||
|
||||
\begin{lstlisting}[
|
||||
language={C},
|
||||
caption={基本调度过程},
|
||||
label={code-c-sample},
|
||||
]
|
||||
void MyTask (void)
|
||||
{
|
||||
while (1) {
|
||||
Wait for an event to occur;
|
||||
Perform task operation;
|
||||
}
|
||||
}
|
||||
\end{lstlisting}
|
||||
|
||||
如上面代码所示，任务(Task)都是等待event，然后处理事务。任何一个任务得以运行，都是因为它收到了一个Event，这个Event可能是一个中断、也可能是超时到期、还有可能是其他任务发出的IPC信号，继续追查发出IPC信号的任务最后的源头Event肯定是一个外部设备硬件中断或者是内部的Timer中断。中断引起了Event传递，形成了逐个运行多个任务的链条(Chain)。一个系统内部会存在很多条这种链条。
|
||||
|
||||
对实时(Real Time)系统来说，不仅仅要求OS能提供多任务环境，更要求任务能在极短的时间之内响应外部的中断事件。
|
||||
|
||||
对于终端节点来说硬实时通讯较好实现，利用时钟定时中断即可强制切换到高级别消息发送，但是终端节点一般作为信息发送和执行节点，不具备逻辑处理功能，在整体通讯延迟受最慢一级也就是逻辑处理层一般也是主机节点影响最大，为处理此问题，对消息进行分级，高优先级消息会先触发中断响应，并切换到执行状态,且不可被抢占。
|
||||
|
||||
|
||||
\section{终端通信}
|
||||
|
||||
\section{性能分析}
|
||||
163
data/chapter4.tex
Normal file
163
data/chapter4.tex
Normal file
@ -0,0 +1,163 @@
|
||||
|
||||
\chapter{知识模型}
|
||||
|
||||
\section{基本模型}
|
||||
|
||||
在建立数字孪生虚拟世界过程中，会有大大小小的规则、算法等知识纳入其中，任何规则算法归纳来讲都是描述任意虚拟或实体对象相关作用关系。本文归纳了这些规则、算法的共同特征，建立了一个一般性的知识模型，该模型是一个动态模型，其知识求解过程可根据特点纳入平台内运算或使用独立进程进行运算求解。
|
||||
基本模型需要先建立三个外部特征，触发域、输入域、输出域。触发域主要用于设定触发求解过程的条件。输入域是指定该模型需要哪些虚拟/实体对象的什么参数。输出域是指定该模型输入影响范围和参数。
|
||||
基本模型内部求解过程可以根据类型和功能特点选择提交公式或算法代码，或直接运行独立的求解程序。
|
||||
|
||||
\section{知识分类}
|
||||
|
||||
对于不同的知识或者说规则，根据其作用域和功能特点，将其分为现实类知识、虚拟类知识、仿真类知识
|
||||
|
||||
\subsection{现实类知识}
|
||||
|
||||
该类知识是具体场景下最底层知识，其触发域和输入域仅能为实体对象数据,虚拟场景运行与否不影响该类知识触发和生效作用。
|
||||
|
||||
\subsection{仿真类知识}
|
||||
|
||||
该类知识为虚拟环境中与实体对象对应的虚拟对象的数据的关联知识，其输出域可以设定于虚拟世界，也可作用于现实世界。
|
||||
|
||||
\subsection{虚拟类知识}
|
||||
该类知识其输出域仅能作用于虚拟世界。
|
||||
|
||||
\section{碰撞检测}
|
||||
碰撞检测目前定义为虚拟类知识，暂时其输出域数据无法作用于现实世界，主要用于虚拟世界用户交互检测。
|
||||
为了简化物体之间的碰撞检测运算，通常会对物体创建一个规则的几何外形将其包围。在本系统中，碰撞检测中将物体分为三种检测模型，点、AABB、球体。其中，AABB（axis-aligned bounding box）包围盒被称为轴对齐包围盒。
|
||||
|
||||
轴对齐包围盒是判断两个物体是否重叠的最快算法，物体被包裹在一个非旋转的（因此轴对齐的）盒中，并检查这些盒在三维坐标空间中的位置，以确定它们是否重叠。
|
||||
|
||||
由于性能原因，轴对齐是有一些约束的。两个非旋转的盒子之间是否重叠可以通过逻辑比较进行检查，而旋转的盒子则需要三角运算，这会导致性能下降。如果你有旋转的物体，可以通过修改边框的尺寸，这样盒子仍可以包裹物体，或者选择使用另一种边界几何类型，比如球体 (球体旋转，形状不会变)。
|
||||
|
||||
\subsection{点与AABB}
|
||||
如果检测到一个点是否在 AABB 内部就非常简单了 — 我们只需要检查这个点的坐标是否在 AABB 内; 分别考虑到每种坐标轴。如果假设 $P_x$, $P_y$ 和 $P_z$ 是点的坐标, $B_{minX} - B_{maxX}$, $B_{minY} - B_{maxY}$, 和$B_{minZ}–B_{maxZ}$ 是 AABB 的每一个坐标轴的范围，我们可以使用以下公式计算两者之间的碰撞是否发生：
|
||||
|
||||
\begin{lstlisting}[
|
||||
language={},
|
||||
label={code-js-sample},
|
||||
]
|
||||
function isPointInsideAABB(point, box) {
|
||||
return (point.x >= box.minX && point.x <= box.maxX) &&
|
||||
(point.y >= box.minY && point.y <= box.maxY) &&
|
||||
(point.z >= box.minY && point.z <= box.maxZ);
|
||||
}
|
||||
\end{lstlisting}
|
||||
|
||||
\subsection{AABB与AABB}
|
||||
|
||||
检查一个 AABB 是否和另一个 AABB 相交类似于检测两个点一样。我们只需要基于每一条坐标轴并利用盒子的边缘去检测。
|
||||
|
||||
\begin{lstlisting}[
|
||||
language={},
|
||||
label={code-js-sample},
|
||||
]
|
||||
function intersect(a, b) {
|
||||
return (a.minX <= b.maxX && a.maxX >= b.minX) &&
|
||||
(a.minY <= b.maxY && a.maxY >= b.minY) &&
|
||||
(a.minZ <= b.maxZ && a.maxZ >= b.minZ);
|
||||
}
|
||||
\end{lstlisting}
|
||||
|
||||
|
||||
\section{刚体运动力学模型}
|
||||
|
||||
在虚拟世界中为关联现实设备运动状态，需要根据已有的传感器数据，如加速度、里程信息等估计实体对象运动姿态，或者由虚拟对象指导影响实体对象运动，两者相互作用皆需要实现基本的刚体运动。
|
||||
|
||||
刚体的运动主要基于牛顿三大定律来模拟:
|
||||
\begin{itemize}
|
||||
\item 1.惯性 物体在不受力时,总是保持速度不变.
|
||||
\item 2.力,质量,加速度力在物体上产生加速度,满足$F = ma$.
|
||||
\item 3.力的作用是相互的
|
||||
\end{itemize}
|
||||
|
||||
|
||||
基于牛顿三大定律,在计算机中来模拟刚体的运动,物理引擎来模拟的流程大致都是这样的:
|
||||
|
||||
对于每个物体,使用循环的方式来模拟:
|
||||
|
||||
|
||||
|
||||
% 流程图定义基本形状
|
||||
\tikzstyle{startstop} = [rectangle, rounded corners, minimum width = 2cm, minimum height=1cm,text centered, draw = black]
|
||||
\tikzstyle{io} = [trapezium, trapezium left angle=70, trapezium right angle=110, minimum width=2cm, minimum height=1cm, text centered, draw=black]
|
||||
\tikzstyle{process} = [rectangle, minimum width=3cm, minimum height=1cm, text centered, draw=black]
|
||||
\tikzstyle{decision} = [diamond, aspect = 3, text centered, draw=black]
|
||||
% 箭头形式
|
||||
\tikzstyle{arrow} = [->,>=stealth]
|
||||
|
||||
\begin{center}
|
||||
\begin{tikzpicture}[node distance=0.5cm]
|
||||
%定义流程图具体形状
|
||||
\node[startstop](start){Start};
|
||||
\node[io, below of = start, yshift = -1cm](in1){分析受力};
|
||||
\node[process, below of = in1, yshift = -1cm](pro1){更新速度和位置};
|
||||
\node[process, below of = pro1, yshift = -1cm](pro2){碰撞检测};
|
||||
\node[io, below of = pro2, yshift = -1cm](out1){解决约束};
|
||||
\node[decision, below of = out1, yshift = -1cm](dec1){到达稳态};
|
||||
\node[startstop, below of = dec1, yshift = -1cm](stop){显示结果};
|
||||
\coordinate (point1) at (-3cm, -6cm);
|
||||
%连接具体形状
|
||||
\draw [arrow] (start) -- (in1);
|
||||
\draw [arrow] (in1) -- (pro1);
|
||||
\draw [arrow] (pro1) -- (pro2);
|
||||
\draw [arrow] (pro1) -- (out1);
|
||||
\draw [arrow] (out1) -- (dec1);
|
||||
|
||||
\draw (dec1) -- node [above] {N} (point1);
|
||||
\draw [arrow] (point1) |- (in1);
|
||||
\draw [arrow] (dec1) -- node [right] {Y} (stop);
|
||||
\end{tikzpicture}
|
||||
\end{center}
|
||||
|
||||
\subsection{理想粒子的运动}
|
||||
|
||||
先不考虑物体的形状和旋转,把物体当成理想粒子来对待,根据牛顿定律来循环计算物体的速度和位置:
|
||||
\[ dt = t_{i+1} - t_{i} \]
|
||||
\[ v(t_{i+1}) = v(t_{i}) + (\frac{f(t_{i})}{m})dt \]
|
||||
\[ p(t_{i+1}) = v(t_{i}) + v(t_{i+1})dt \]
|
||||
|
||||
将其泰勒展开
|
||||
|
||||
\[ p(t_{i+1}) = p(t_{i}) + p^{'}(t_{i})dt + p^{''}(t_{i})\frac{dt^{2}}{2!} + p^{'''}(t_{i})\frac{dt^{3}}{3!} + ... \]
|
||||
|
||||
对于浏览器按像素点实时位置渲染精度而言，3阶泰勒展开已符合精度要求。
|
||||
|
||||
|
||||
|
||||
\subsection{3d物体旋转运动}
|
||||
|
||||
惯性张量
|
||||
|
||||
在三维空间中任取一点$Q$ 及一个直角坐标系$Q_{xyz}$,可以得到物体的惯性张量:
|
||||
|
||||
\begin{equation}
|
||||
I ={
|
||||
\left[ \begin{array}{ccc}
|
||||
I_{xx} & I_{xy} & I_{xz}\\
|
||||
I_{yz} & I_{yy} & I_{yz}\\
|
||||
I_{zx} & I_{zy} & I_{zz}
|
||||
\end{array}
|
||||
\right ]}
|
||||
\end{equation}
|
||||
|
||||
对角元素$I_{xx}$,$I_{yy}$,$I_{yy}$是物体分别相对于$x$，$y$，$z$轴的转动惯量。
|
||||
\[ I_{xx} = \int{(r_{y}^{2}+r_z^2)dm} \]
|
||||
\[ I_{yy} = \int{(r_{x}^{2}+r_z^2)dm} \]
|
||||
\[ I_{zz} = \int{(r_{x}^{2}+r_y^2)dm} \]
|
||||
|
||||
计算惯量积
|
||||
\[ I_{xy} = I_{yx} = - \int{(r_x r_y)dm} \]
|
||||
\[ I_{xz} = I_{zx} = - \int{(r_x r_z)dm} \]
|
||||
\[ I_{yz} = I_{zy} = - \int{(r_z r_y)dm} \]
|
||||
|
||||
根据惯性张量计算力矩$\tau$，角将速度$d\omega$，角速度$\omega$。
|
||||
\[ \tau = \frac{dL}{dt} = I \frac{d\omega}{dt} \]
|
||||
\[ d\omega = I^{-1} \tau dt \]
|
||||
\[ \omega(t_{i+1}) = \omega(t_i) + (I^{-1} \tau(t_i)) dt \]
|
||||
|
||||
用四元数$q$来表示刚体的旋转状态，刚体在$dt$时间内沿着$\omega$旋转了$|\omega dt|$的角度，得到
|
||||
\begin{equation}
|
||||
q(t_{i+1}) = q(t_i) * [\cos{\frac{|\omega dt|}{2}},\sin{\frac{|\omega dt|}{2}}\frac{\omega}{|\omega|}]
|
||||
\end{equation}
|
||||
|
||||
9
data/chapter5.tex
Normal file
9
data/chapter5.tex
Normal file
@ -0,0 +1,9 @@
|
||||
\chapter{状态与事件模型}
|
||||
|
||||
\section{状态机制}
|
||||
|
||||
\section{时序模型}
|
||||
|
||||
\section{事件模型}
|
||||
|
||||
\section{预测算法}
|
||||
@ -2,15 +2,3 @@
|
||||
\chapter*{结论\markboth{结论}{}}
|
||||
\addcontentsline{toc}{chapter}{结论}
|
||||
|
||||
本文主要介绍使用\LaTeX{}进行撰写论文的方法，文中范例丰富，涵盖基本的论文使用，在使用本\LaTeX{}模板时
|
||||
可直接复制后进行内容的替换更改即可使用。
|
||||
|
||||
在第一章主要介绍了\LaTeX{}的背景、本模板的维护者信息以及开源协议等；
|
||||
在第二章介绍了各个操作系统平台下\LaTeX{}的配置方法；
|
||||
在第三章介绍了各\LaTeX{}版本及软件的下载地址；
|
||||
在第四章介绍了\LaTeX{}的基本常用语法以及代码示例，高阶使用技巧等；
|
||||
|
||||
\ldots\ldots\ldots
|
||||
|
||||
通过使用本模块来完成论文，可以基本掌握\LaTeX{}的使用，也在最小学习成本的基础上满足规范的论文格式，省去
|
||||
后期调格式之苦，使作者更专注于论文，亦可更高效的完成论文。
|
||||
|
||||
@ -10,10 +10,14 @@
|
||||
\item[physical entity] 物理对象
|
||||
\item[virtual entity] 虚拟对象
|
||||
\item[physical domain(space)] 物理域(物理空间)
|
||||
\item[$E$] 能量
|
||||
\item[$m$] 质量
|
||||
\item[$c$] 光速
|
||||
\item[$P$] 概率
|
||||
\item[$T$] 时间
|
||||
\item[$v$] 速度
|
||||
\item[$L$] 角动量
|
||||
\item[$I$] 惯性张量
|
||||
\item[$\tau$] 力矩
|
||||
\item[$\omega$] 角速度
|
||||
% \item[$E$] 能量
|
||||
% \item[$m$] 质量
|
||||
% \item[$c$] 光速
|
||||
% \item[$P$] 概率
|
||||
% \item[$T$] 时间
|
||||
% \item[$v$] 速度
|
||||
\end{denotation}
|
||||
|
||||
@ -4,4 +4,4 @@
|
||||
\addcontentsline{toc}{chapter}{参考文献}
|
||||
\nocite{*}
|
||||
\bibliography{data/bibs}
|
||||
\cleardoublepage
|
||||
\cleardoublepage
|
||||
|
||||
BIN
figure/f1.png
Normal file
BIN
figure/f1.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 140 KiB |
BIN
figure/f2.png
Normal file
BIN
figure/f2.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 119 KiB |
BIN
figure/f3.png
Normal file
BIN
figure/f3.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 422 KiB |
1407
figure/image.pdf
1407
figure/image.pdf
File diff suppressed because one or more lines are too long
2160
gbt7714-author-year.bst
Normal file
2160
gbt7714-author-year.bst
Normal file
File diff suppressed because it is too large
Load Diff
1983
gbt7714-numerical.bst
Normal file
1983
gbt7714-numerical.bst
Normal file
File diff suppressed because it is too large
Load Diff
296
gbt7714.sty
Normal file
296
gbt7714.sty
Normal file
@ -0,0 +1,296 @@
|
||||
%%
|
||||
%% This is file `gbt7714.sty',
|
||||
%% generated with the docstrip utility.
|
||||
%%
|
||||
%% The original source files were:
|
||||
%%
|
||||
%% gbt7714.dtx (with options: `package')
|
||||
%% -------------------------------------------------------------------
|
||||
%% GB/T 7714-2015 BibTeX Style
|
||||
%% https://github.com/CTeX-org/gbt7714-bibtex-style
|
||||
%% Version: 2020/03/14 v2.0.1
|
||||
%% -------------------------------------------------------------------
|
||||
%% Copyright (C) 2016-2020 by Zeping Lee <zepinglee AT gmail.com>
|
||||
%% -------------------------------------------------------------------
|
||||
%% This file may be distributed and/or modified under the
|
||||
%% conditions of the LaTeX Project Public License, either version 1.3c
|
||||
%% of this license or (at your option) any later version.
|
||||
%% The latest version of this license is in
|
||||
%% https://www.latex-project.org/lppl.txt
|
||||
%% and version 1.3c or later is part of all distributions of LaTeX
|
||||
%% version 2005/12/01 or later.
|
||||
%% -------------------------------------------------------------------
|
||||
\NeedsTeXFormat{LaTeX2e}[1999/12/01]
|
||||
\ProvidesPackage{gbt7714}
|
||||
[2020/03/14 v2.0.1 GB/T 7714-2015 BibTeX Style]
|
||||
\newif\ifgbt@legacy@interface
|
||||
\newif\ifgbt@mmxv
|
||||
\newif\ifgbt@numerical
|
||||
\newif\ifgbt@super
|
||||
\newcommand\gbt@obselete@option[1]{%
|
||||
\PackageWarning{gbt7714}{The option "#1" is obselete}%
|
||||
}
|
||||
\DeclareOption{2015}{%
|
||||
\gbt@obselete@option{2015}%
|
||||
\gbt@legacy@interfacetrue
|
||||
\gbt@mmxvtrue
|
||||
}
|
||||
\DeclareOption{2005}{%
|
||||
\gbt@obselete@option{2005}%
|
||||
\gbt@legacy@interfacetrue
|
||||
\gbt@mmxvfalse
|
||||
}
|
||||
\DeclareOption{super}{%
|
||||
\gbt@obselete@option{super}%
|
||||
\gbt@legacy@interfacetrue
|
||||
\gbt@numericaltrue
|
||||
\gbt@supertrue
|
||||
}
|
||||
\DeclareOption{numbers}{%
|
||||
\gbt@obselete@option{numbers}%
|
||||
\gbt@legacy@interfacetrue
|
||||
\gbt@numericaltrue
|
||||
\gbt@superfalse
|
||||
}
|
||||
\DeclareOption{authoryear}{%
|
||||
\gbt@obselete@option{authoryear}%
|
||||
\gbt@legacy@interfacetrue
|
||||
\gbt@numericalfalse
|
||||
}
|
||||
\DeclareOption*{\PassOptionsToPackage{\CurrentOption}{natbib}}
|
||||
\ProcessOptions\relax
|
||||
% \RequirePackage[compress]{natbib}
|
||||
\setcitestyle{compress}
|
||||
\RequirePackage{url}
|
||||
\renewcommand\newblock{\space}
|
||||
\newcommand\bibstyle@super{\bibpunct{[}{]}{,}{s}{,}{\textsuperscript{,}}}
|
||||
\newcommand\bibstyle@numbers{\bibpunct{[}{]}{,}{n}{,}{,}}
|
||||
\newcommand\bibstyle@authoryear{\bibpunct{(}{)}{;}{a}{,}{,}}
|
||||
\newcommand\bibstyle@inline{\bibstyle@numbers}
|
||||
\@namedef{bibstyle@gbt7714-numerical}{\bibstyle@super}
|
||||
\@namedef{bibstyle@gbt7714-author-year}{\bibstyle@authoryear}
|
||||
\@namedef{bibstyle@gbt7714-2005-numerical}{\bibstyle@super}
|
||||
\@namedef{bibstyle@gbt7714-2005-author-year}{\bibstyle@authoryear}
|
||||
\def\NAT@citexnum[#1][#2]#3{%
|
||||
\NAT@reset@parser
|
||||
\NAT@sort@cites{#3}%
|
||||
\NAT@reset@citea
|
||||
\@cite{\def\NAT@num{-1}\let\NAT@last@yr\relax\let\NAT@nm\@empty
|
||||
\@for\@citeb:=\NAT@cite@list\do
|
||||
{\@safe@activestrue
|
||||
\edef\@citeb{\expandafter\@firstofone\@citeb\@empty}%
|
||||
\@safe@activesfalse
|
||||
\@ifundefined{b@\@citeb\@extra@b@citeb}{%
|
||||
{\reset@font\bfseries?}
|
||||
\NAT@citeundefined\PackageWarning{natbib}%
|
||||
{Citation `\@citeb' on page \thepage \space undefined}}%
|
||||
{\let\NAT@last@num\NAT@num\let\NAT@last@nm\NAT@nm
|
||||
\NAT@parse{\@citeb}%
|
||||
\ifNAT@longnames\@ifundefined{bv@\@citeb\@extra@b@citeb}{%
|
||||
\let\NAT@name=\NAT@all@names
|
||||
\global\@namedef{bv@\@citeb\@extra@b@citeb}{}}{}%
|
||||
\fi
|
||||
\ifNAT@full\let\NAT@nm\NAT@all@names\else
|
||||
\let\NAT@nm\NAT@name\fi
|
||||
\ifNAT@swa
|
||||
\@ifnum{\NAT@ctype>\@ne}{%
|
||||
\@citea
|
||||
\NAT@hyper@{\@ifnum{\NAT@ctype=\tw@}{\NAT@test{\NAT@ctype}}{\NAT@alias}}%
|
||||
}{%
|
||||
\@ifnum{\NAT@cmprs>\z@}{%
|
||||
\NAT@ifcat@num\NAT@num
|
||||
{\let\NAT@nm=\NAT@num}%
|
||||
{\def\NAT@nm{-2}}%
|
||||
\NAT@ifcat@num\NAT@last@num
|
||||
{\@tempcnta=\NAT@last@num\relax}%
|
||||
{\@tempcnta\m@ne}%
|
||||
\@ifnum{\NAT@nm=\@tempcnta}{%
|
||||
\@ifnum{\NAT@merge>\@ne}{}{\NAT@last@yr@mbox}%
|
||||
}{%
|
||||
\advance\@tempcnta by\@ne
|
||||
\@ifnum{\NAT@nm=\@tempcnta}{%
|
||||
% \ifx\NAT@last@yr\relax
|
||||
% \def@NAT@last@yr{\@citea}%
|
||||
% \else
|
||||
% \def@NAT@last@yr{--\NAT@penalty}%
|
||||
% \fi
|
||||
\def@NAT@last@yr{-\NAT@penalty}%
|
||||
}{%
|
||||
\NAT@last@yr@mbox
|
||||
}%
|
||||
}%
|
||||
}{%
|
||||
\@tempswatrue
|
||||
\@ifnum{\NAT@merge>\@ne}{\@ifnum{\NAT@last@num=\NAT@num\relax}{\@tempswafalse}{}}{}%
|
||||
\if@tempswa\NAT@citea@mbox\fi
|
||||
}%
|
||||
}%
|
||||
\NAT@def@citea
|
||||
\else
|
||||
\ifcase\NAT@ctype
|
||||
\ifx\NAT@last@nm\NAT@nm \NAT@yrsep\NAT@penalty\NAT@space\else
|
||||
\@citea \NAT@test{\@ne}\NAT@spacechar\NAT@mbox{\NAT@super@kern\NAT@@open}%
|
||||
\fi
|
||||
\if*#1*\else#1\NAT@spacechar\fi
|
||||
\NAT@mbox{\NAT@hyper@{{\citenumfont{\NAT@num}}}}%
|
||||
\NAT@def@citea@box
|
||||
\or
|
||||
\NAT@hyper@citea@space{\NAT@test{\NAT@ctype}}%
|
||||
\or
|
||||
\NAT@hyper@citea@space{\NAT@test{\NAT@ctype}}%
|
||||
\or
|
||||
\NAT@hyper@citea@space\NAT@alias
|
||||
\fi
|
||||
\fi
|
||||
}%
|
||||
}%
|
||||
\@ifnum{\NAT@cmprs>\z@}{\NAT@last@yr}{}%
|
||||
\ifNAT@swa\else
|
||||
% \@ifnum{\NAT@ctype=\z@}{%
|
||||
% \if*#2*\else\NAT@cmt#2\fi
|
||||
% }{}%
|
||||
\NAT@mbox{\NAT@@close}%
|
||||
\@ifnum{\NAT@ctype=\z@}{%
|
||||
\if*#2*\else\textsuperscript{#2}\fi
|
||||
}{}%
|
||||
\fi
|
||||
}{#1}{#2}%
|
||||
}%
|
||||
\renewcommand\NAT@citesuper[3]{\ifNAT@swa
|
||||
\if*#2*\else#2\NAT@spacechar\fi
|
||||
\unskip\kern\p@\textsuperscript{\NAT@@open#1\NAT@@close\if*#3*\else#3\fi}%
|
||||
\else #1\fi\endgroup}
|
||||
\def\NAT@citex%
|
||||
[#1][#2]#3{%
|
||||
\NAT@reset@parser
|
||||
\NAT@sort@cites{#3}%
|
||||
\NAT@reset@citea
|
||||
\@cite{\let\NAT@nm\@empty\let\NAT@year\@empty
|
||||
\@for\@citeb:=\NAT@cite@list\do
|
||||
{\@safe@activestrue
|
||||
\edef\@citeb{\expandafter\@firstofone\@citeb\@empty}%
|
||||
\@safe@activesfalse
|
||||
\@ifundefined{b@\@citeb\@extra@b@citeb}{\@citea%
|
||||
{\reset@font\bfseries ?}\NAT@citeundefined
|
||||
\PackageWarning{natbib}%
|
||||
{Citation `\@citeb' on page \thepage \space undefined}\def\NAT@date{}}%
|
||||
{\let\NAT@last@nm=\NAT@nm\let\NAT@last@yr=\NAT@year
|
||||
\NAT@parse{\@citeb}%
|
||||
\ifNAT@longnames\@ifundefined{bv@\@citeb\@extra@b@citeb}{%
|
||||
\let\NAT@name=\NAT@all@names
|
||||
\global\@namedef{bv@\@citeb\@extra@b@citeb}{}}{}%
|
||||
\fi
|
||||
\ifNAT@full\let\NAT@nm\NAT@all@names\else
|
||||
\let\NAT@nm\NAT@name\fi
|
||||
\ifNAT@swa\ifcase\NAT@ctype
|
||||
\if\relax\NAT@date\relax
|
||||
\@citea\NAT@hyper@{\NAT@nmfmt{\NAT@nm}\NAT@date}%
|
||||
\else
|
||||
\ifx\NAT@last@nm\NAT@nm\NAT@yrsep
|
||||
\ifx\NAT@last@yr\NAT@year
|
||||
\def\NAT@temp{{?}}%
|
||||
\ifx\NAT@temp\NAT@exlab\PackageWarningNoLine{natbib}%
|
||||
{Multiple citation on page \thepage: same authors and
|
||||
year\MessageBreak without distinguishing extra
|
||||
letter,\MessageBreak appears as question mark}\fi
|
||||
\NAT@hyper@{\NAT@exlab}%
|
||||
\else\unskip\NAT@spacechar
|
||||
\NAT@hyper@{\NAT@date}%
|
||||
\fi
|
||||
\else
|
||||
\@citea\NAT@hyper@{%
|
||||
\NAT@nmfmt{\NAT@nm}%
|
||||
\hyper@natlinkbreak{%
|
||||
\NAT@aysep\NAT@spacechar}{\@citeb\@extra@b@citeb
|
||||
}%
|
||||
\NAT@date
|
||||
}%
|
||||
\fi
|
||||
\fi
|
||||
\or\@citea\NAT@hyper@{\NAT@nmfmt{\NAT@nm}}%
|
||||
\or\@citea\NAT@hyper@{\NAT@date}%
|
||||
\or\@citea\NAT@hyper@{\NAT@alias}%
|
||||
\fi \NAT@def@citea
|
||||
\else
|
||||
\ifcase\NAT@ctype
|
||||
\if\relax\NAT@date\relax
|
||||
\@citea\NAT@hyper@{\NAT@nmfmt{\NAT@nm}}%
|
||||
\else
|
||||
\ifx\NAT@last@nm\NAT@nm\NAT@yrsep
|
||||
\ifx\NAT@last@yr\NAT@year
|
||||
\def\NAT@temp{{?}}%
|
||||
\ifx\NAT@temp\NAT@exlab\PackageWarningNoLine{natbib}%
|
||||
{Multiple citation on page \thepage: same authors and
|
||||
year\MessageBreak without distinguishing extra
|
||||
letter,\MessageBreak appears as question mark}\fi
|
||||
\NAT@hyper@{\NAT@exlab}%
|
||||
\else
|
||||
\unskip\NAT@spacechar
|
||||
\NAT@hyper@{\NAT@date}%
|
||||
\fi
|
||||
\else
|
||||
\@citea\NAT@hyper@{%
|
||||
\NAT@nmfmt{\NAT@nm}%
|
||||
\hyper@natlinkbreak{\NAT@spacechar\NAT@@open\if*#1*\else#1\NAT@spacechar\fi}%
|
||||
{\@citeb\@extra@b@citeb}%
|
||||
\NAT@date
|
||||
}%
|
||||
\fi
|
||||
\fi
|
||||
\or\@citea\NAT@hyper@{\NAT@nmfmt{\NAT@nm}}%
|
||||
\or\@citea\NAT@hyper@{\NAT@date}%
|
||||
\or\@citea\NAT@hyper@{\NAT@alias}%
|
||||
\fi
|
||||
\if\relax\NAT@date\relax
|
||||
\NAT@def@citea
|
||||
\else
|
||||
\NAT@def@citea@close
|
||||
\fi
|
||||
\fi
|
||||
}}\ifNAT@swa\else
|
||||
% \if*#2*\else\NAT@cmt#2\fi
|
||||
\if\relax\NAT@date\relax\else\NAT@@close\fi
|
||||
\if*#2*\else\textsuperscript{#2}\fi
|
||||
\fi}{#1}{#2}}
|
||||
\renewcommand\NAT@cite%
|
||||
[3]{\ifNAT@swa\NAT@@open\if*#2*\else#2\NAT@spacechar\fi
|
||||
#1\NAT@@close\if*#3*\else\textsuperscript{#3}\fi\else#1\fi\endgroup}
|
||||
\renewcommand\@biblabel[1]{[#1]\hfill}
|
||||
\g@addto@macro\UrlBreaks{%
|
||||
\do0\do1\do2\do3\do4\do5\do6\do7\do8\do9%
|
||||
\do\A\do\B\do\C\do\D\do\E\do\F\do\G\do\H\do\I\do\J\do\K\do\L\do\M
|
||||
\do\N\do\O\do\P\do\Q\do\R\do\S\do\T\do\U\do\V\do\W\do\X\do\Y\do\Z
|
||||
\do\a\do\b\do\c\do\d\do\e\do\f\do\g\do\h\do\i\do\j\do\k\do\l\do\m
|
||||
\do\n\do\o\do\p\do\q\do\r\do\s\do\t\do\u\do\v\do\w\do\x\do\y\do\z
|
||||
}
|
||||
\Urlmuskip=0mu plus 0.1mu
|
||||
\newif\ifgbt@bib@style@written
|
||||
\@ifpackageloaded{chapterbib}{}{%
|
||||
\def\bibliography#1{%
|
||||
\ifgbt@bib@style@written\else
|
||||
\bibliographystyle{gbt7714-numerical}%
|
||||
\fi
|
||||
\if@filesw
|
||||
\immediate\write\@auxout{\string\bibdata{\zap@space#1 \@empty}}%
|
||||
\fi
|
||||
\@input@{\jobname.bbl}}
|
||||
\def\bibliographystyle#1{%
|
||||
\gbt@bib@style@writtentrue
|
||||
\ifx\@begindocumenthook\@undefined\else
|
||||
\expandafter\AtBeginDocument
|
||||
\fi
|
||||
{\if@filesw
|
||||
\immediate\write\@auxout{\string\bibstyle{#1}}%
|
||||
\fi}%
|
||||
}%
|
||||
}
|
||||
\ifgbt@legacy@interface
|
||||
\ifgbt@numerical
|
||||
\ifgbt@super\else
|
||||
\citestyle{numbers}
|
||||
\fi
|
||||
\bibliographystyle{gbt7714-numerical}
|
||||
\else
|
||||
\bibliographystyle{gbt7714-author-year}
|
||||
\fi
|
||||
\fi
|
||||
39
main.tex
39
main.tex
@ -1,7 +1,15 @@
|
||||
% !Mode:: "TeX:UTF-8"
|
||||
\documentclass[master,openright,twoside,color,AutoFakeBold=true]{buaathesis}
|
||||
\usepackage[UTF8]{ctex}
|
||||
|
||||
\usepackage{xcolor}
|
||||
\usepackage{tikz}
|
||||
\usetikzlibrary{arrows,shapes,chains}
|
||||
|
||||
% 参考文献
|
||||
\usepackage{gbt7714}
|
||||
% 参考文献输出方式，numerical为按照出现顺序，authoryear为按照作者姓名和年份
|
||||
\citestyle{numerical}
|
||||
% \citestyle{authoryear}
|
||||
|
||||
\begin{document}
|
||||
|
||||
@ -9,30 +17,30 @@
|
||||
\include{data/com_info}
|
||||
\include{data/master/master_info}
|
||||
|
||||
% 中英封面、提名页、授权书
|
||||
\maketitle
|
||||
|
||||
% 前言页眉页脚样式
|
||||
\pagestyle{frontmatter}
|
||||
|
||||
% 摘要
|
||||
\include{data/abstract}
|
||||
% 目录、插图目录、表格目录
|
||||
\tableofcontents
|
||||
\listoffigures
|
||||
% \listoftables
|
||||
\listoftables
|
||||
% 符号表
|
||||
\include{data/master/denotation}
|
||||
|
||||
|
||||
% 正文页码样式
|
||||
\mainmatter
|
||||
% 正文页眉页脚样式
|
||||
\pagestyle{mainmatter}
|
||||
|
||||
|
||||
% 正文
|
||||
\include{data/chapter1-intro}
|
||||
\include{data/chapter2-config}
|
||||
\include{data/chapter2}
|
||||
\include{data/chapter3}
|
||||
\include{data/chapter4}
|
||||
\include{data/chapter5}
|
||||
% \include{data/chapter3-download}
|
||||
% \include{data/chapter4-basic}
|
||||
% \include{data/chapter5-usage}
|
||||
@ -41,18 +49,17 @@
|
||||
|
||||
% 参考文献
|
||||
\include{data/reference}
|
||||
|
||||
% 附录
|
||||
\appendix
|
||||
\include{data/appendix1-faq}
|
||||
\include{data/appendix2-contactus}
|
||||
% \appendix
|
||||
% \include{data/appendix1-faq}
|
||||
% \include{data/appendix2-contactus}
|
||||
|
||||
% 附页标题样式
|
||||
\backmatter
|
||||
% \backmatter
|
||||
|
||||
% 附页
|
||||
\include{data/master/back1-achievement}
|
||||
\include{data/master/back2-acknowledgement}
|
||||
\include{data/master/back3-aboutauthor}
|
||||
|
||||
% \include{data/master/back1-achievement}
|
||||
% \include{data/master/back2-acknowledgement}
|
||||
% \include{data/master/back3-aboutauthor}
|
||||
\end{document}
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user