From d7d5ce38c6a19ef314e0c2eb2e1e0559c3d28dda Mon Sep 17 00:00:00 2001 From: "zhouzhihao@ihep.ac.cn" <zhouzhihao@ihep.ac.cn> Date: Sat, 7 Dec 2024 08:36:10 +0000 Subject: [PATCH] =?UTF-8?q?=E4=BF=AE=E6=94=B9README?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- README.md | 94 ++----------------------------------------------------- 1 file changed, 2 insertions(+), 92 deletions(-) diff --git a/README.md b/README.md index ef0a769..7bbcfc0 100644 --- a/README.md +++ b/README.md @@ -1,93 +1,3 @@ -# QYLTO +# QYLTSO - - -## Getting started - -To make it easy for you to get started with GitLab, here's a list of recommended next steps. - -Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)! - -## Add your files - -- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files -- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command: - -``` -cd existing_repo -git remote add origin https://code.ihep.ac.cn/zhouzhihao/qylto.git -git branch -M main -git push -uf origin main -``` - -## Integrate with your tools - -- [ ] [Set up project integrations](https://code.ihep.ac.cn/zhouzhihao/qylto/-/settings/integrations) - -## Collaborate with your team - -- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/) -- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html) -- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically) -- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/) -- [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html) - -## Test and Deploy - -Use the built-in continuous integration in GitLab. - -- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html) -- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/) -- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html) -- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/) -- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html) - -*** - -# Editing this README - -When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template. - -## Suggestions for a good README - -Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information. - -## Name -Choose a self-explaining name for your project. - -## Description -Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors. - -## Badges -On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge. - -## Visuals -Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method. - -## Installation -Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection. - -## Usage -Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README. - -## Support -Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc. - -## Roadmap -If you have ideas for releases in the future, it is a good idea to list them in the README. - -## Contributing -State if you are open to contributions and what your requirements are for accepting them. - -For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self. - -You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser. - -## Authors and acknowledgment -Show your appreciation to those who have contributed to the project. - -## License -For open source projects, say how it is licensed. - -## Project status -If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers. +Geant4鍏佽鐢ㄦ埛閫氳繃鑷畾涔変笁瑙掑舰闈€€佸洓杈瑰舰闈㈡潵鍒涘缓涓€涓狦4TessellatedSolid瀵硅薄浣滀负Solid銆傛垜浠彲浠ュ埄鐢ㄨ繖涓€鐐规潵瀵煎叆3D鍥惧舰銆傚浜庡鏉傜殑锛岄渶瑕佸垱寤哄ぇ閲忛儴浠剁殑鎯呭舰锛孏eant4鎺ㄨ崘浣跨敤GDML鏍煎紡鏉ュ鍏ワ紝鍦ㄥ叾瀹樻柟鎵嬪唽涓紝涔熶粙缁嶄簡鍑犵杈呭姪鏂瑰紡灏哠TEP绛夋牸寮忎繚瀛樹笁缁村浘鍍忔暟鎹鍑轰负GDML鏍煎紡鐨勬枃浠躲€傝繖浜涙柟娉曚腑鐨勬煇浜涜蒋浠舵槸鐢卞叕鍙告垨鑰呮煇浜涙満鏋勫垱寤虹殑锛屽ぇ閮介渶瑕佹垚涓烘敞鍐岀敤鎴凤紝鏈変簺椤圭洰鍙彁渚涚煭鏈熻鍙瘉銆備负浜嗚拷姹傜畝鍗曞拰杞婚噺鍖栵紝鎴戜滑鏈€缁堝喅瀹氫笉浣跨敤杩欎簺鏂规硶锛屾敼涓鸿嚜宸卞鍑轰笁瑙掑舰鏉ユ嫾鎺ヤ竴涓猄olid锛屾墍浠ュ垱寤轰簡杩欎釜Quickly Yield Lots of Tessellated Solid Objects锛圦YLTO锛夐」鐩€傛椤圭洰浣跨敤FreeCAD鐨凱ython API灏哠TP/STEP鏍煎紡鐨勬枃浠跺鍑轰负stl鏂囦欢锛岀劧鍚庡皢stl鏂囦欢瀵煎嚭涓篶sv鏍煎紡鐨勬枃浠讹紝鏈€缁堟嫾鎺ユ垚涓€涓狦4TessellatedSolid瀵硅薄銆傝缃潗鏂欙紝鏀剧疆绛夊姛鑳戒篃浼氶€愭瀹炵幇銆� \ No newline at end of file -- GitLab