BramVanroy/stack_md_lid · Datasets at Hugging Face

e93f6da5c100870c7b6de642bfcd413a855423f9

276

md

Markdown

docs/references/pubsub-websocket-subprotocol.md

lovettchris/azure-webpubsub

24ad795d2a561d504d44104f98f9f8909fa9a5e4

[ "MIT" ]

75

2021-04-28T02:33:01.000Z

2022-03-26T10:03:17.000Z

docs/references/pubsub-websocket-subprotocol.md

lovettchris/azure-webpubsub

24ad795d2a561d504d44104f98f9f8909fa9a5e4

[ "MIT" ]

114

2021-04-22T04:20:29.000Z

2022-03-24T16:50:55.000Z

docs/references/pubsub-websocket-subprotocol.md

lovettchris/azure-webpubsub

24ad795d2a561d504d44104f98f9f8909fa9a5e4

[ "MIT" ]

47

2021-04-25T02:44:22.000Z

2022-03-28T09:44:55.000Z

--- redirect_to: https://docs.microsoft.com/azure/azure-web-pubsub/reference-json-webpubsub-subprotocol layout: docs toc: true group: references --- Click [here](https://docs.microsoft.com/azure/azure-web-pubsub/reference-json-webpubsub-subprotocol) for the latest docs.

34.5

121

0.775362

yue_Hant

0.33835

e940103d804244818ff3d6d35fa09f5af5874a69

1,837

md

Markdown

README.md

choumingde/open-sso

9dd7b3e791bb369a41aedb36698a1f9a0c0a7347

[ "Apache-2.0" ]

1

2021-07-15T04:50:29.000Z

README.md

choumingde/open-sso

9dd7b3e791bb369a41aedb36698a1f9a0c0a7347

[ "Apache-2.0" ]

null

README.md

choumingde/open-sso

9dd7b3e791bb369a41aedb36698a1f9a0c0a7347

[ "Apache-2.0" ]

null

# open-sso #### 介绍 {**open-sso统一登录服务/单点登录/集群** 基于Spring Boot 搭建的sso统一登录平台 [https://github.com/choumingde/open-sso](https://github.com/choumingde/open-sso)} #### 软件架构 Java 1.8 Maven 3.6.3 Spring Boot 2.1.0.RELEASE Redis 6.2.1 #### 安装教程 # 客户端配置 1.接入方引入 <dependency> <groupId>cn.cmd</groupId> <artifactId>open-sso-starter</artifactId> <version>${project.parent.version}</version> </dependency> 2.修改配置 #sso服务端地址 sso.server.url=http://opensso.cmd.cn:8080 #支持的应用的appId sso.server.appId=demo1 #支持的应用的appSecret sso.server.appSecret=123456 #排除的urls sso.server.excludeUrls= # 服务端配置 1.修改open-sso-server配置 #sso服务端地址 sso.server.url=http://opensso.cmd.cn:8080 #支持的应用的appId sso.server.appId=server1 #支持的应用的appSecret sso.server.appSecret=123456 #排除的urls sso.server.excludeUrls=/login,/logout,/oauth2/*,/custom/*,/assets/* #session存储方式（redis和local） sso.server.session.manager=redis #单点登录超时时间（默认7200） sso.server.timeout=7200 #redis地址 spring.redis.host=opensso.cmd.cn #redis端口 spring.redis.port=6379 #redis密码 spring.redis.password= spring.session.store-type=redis 2.实现接口 1.需要实现 cn.cmd.opensso.server.service.impl.AppServiceImpl 实现接入应用appId和appSecret 2.需要实现 cn.cmd.opensso.server.service.impl.UserServiceImpl 实现用户账号管理 3.修改host文件 127.0.0.1 demo.cmd.cn #测试demo访问地址(http://demo.cmd.cn:8082/demo) 127.0.0.1 opensso.cmd.cn #sso服务器地址(http://opensso.cmd.cn:8080) #### 使用说明 1. open-sso-demo作为参考 2. 尚未支持sso服务端前后端分离 3. 需自行实现用户和接入管理功能 #### 参与贡献 1. choumingde #### 特技 1. 支持单机和集群方式sso登录 #### 致敬 1. 参考 [https://gitee.com/a466350665/smart-sso?_from=gitee_search](https://gitee.com/a466350665/smart-sso?_from=gitee_search) 致敬

20.411111

132

0.668481

yue_Hant

0.160787

e9404b4f9733d46ee763dd8ff7bc4a742f7b7458

1,478

md

Markdown

results/innerfidelity/sbaf-serious/Stax SR-3/README.md

hyshuma/AutoEq

4c3ad3478d6b74fc794bd7d973b330d38da338b9

[ "MIT" ]

1

2020-01-16T14:03:51.000Z

results/innerfidelity/sbaf-serious/Stax SR-3/README.md

hyshuma/AutoEq

4c3ad3478d6b74fc794bd7d973b330d38da338b9

[ "MIT" ]

null

results/innerfidelity/sbaf-serious/Stax SR-3/README.md

hyshuma/AutoEq

4c3ad3478d6b74fc794bd7d973b330d38da338b9

[ "MIT" ]

null

# Stax SR-3 See [usage instructions](https://github.com/jaakkopasanen/AutoEq#usage) for more options and info. ### Parametric EQs In case of using parametric equalizer, apply preamp of **-6.7dB** and build filters manually with these parameters. The first 5 filters can be used independently. When using independent subset of filters, apply preamp of **-7.4dB**. | Type | Fc | Q | Gain | |:--------|:--------|:-----|:--------| | Peaking | 62 Hz | 0.33 | 8.3 dB | | Peaking | 156 Hz | 0.96 | -9.2 dB | | Peaking | 3915 Hz | 0.61 | -3.4 dB | | Peaking | 5864 Hz | 2.03 | 8.8 dB | | Peaking | 8963 Hz | 3.57 | -2.4 dB | | Peaking | 18 Hz | 1.46 | 1.9 dB | | Peaking | 56 Hz | 0.75 | -1.4 dB | | Peaking | 65 Hz | 2.52 | 0.9 dB | | Peaking | 83 Hz | 5.15 | 2.3 dB | ### Fixed Band EQs In case of using fixed band (also called graphic) equalizer, apply preamp of **-8.3dB** (if available) and set gains manually with these parameters. | Type | Fc | Q | Gain | |:--------|:---------|:-----|:--------| | Peaking | 31 Hz | 1.41 | 5.5 dB | | Peaking | 62 Hz | 1.41 | 7.3 dB | | Peaking | 125 Hz | 1.41 | -2.9 dB | | Peaking | 250 Hz | 1.41 | -2.3 dB | | Peaking | 500 Hz | 1.41 | 0.9 dB | | Peaking | 1000 Hz | 1.41 | -0.5 dB | | Peaking | 2000 Hz | 1.41 | -1.9 dB | | Peaking | 4000 Hz | 1.41 | 0.2 dB | | Peaking | 8000 Hz | 1.41 | 1.6 dB | | Peaking | 16000 Hz | 1.41 | -0.4 dB | ### Graphs ![](./Stax%20SR-3.png)

37.897436

98

0.547361

eng_Latn

0.79432

e940bf7d9fe78da3504c0626dbac7c39e460f4a2

2,141

md

Markdown

content/news/2014/08/2014-08-07-parents-get-a-head-start-with-new-mobile-app.md

afeijoo/digitalgov.gov

117098d31802464d9696987980f4a400f3f6654c

[ "CC0-1.0" ]

1

2022-01-23T11:31:14.000Z

content/news/2014/08/2014-08-07-parents-get-a-head-start-with-new-mobile-app.md

afeijoo/digitalgov.gov

117098d31802464d9696987980f4a400f3f6654c

[ "CC0-1.0" ]

null

content/news/2014/08/2014-08-07-parents-get-a-head-start-with-new-mobile-app.md

afeijoo/digitalgov.gov

117098d31802464d9696987980f4a400f3f6654c

[ "CC0-1.0" ]

null

--- slug: parents-get-a-head-start-with-new-mobile-app date: 2014-08-07 13:00:46 -0400 title: Parents Get a Head Start With New Mobile App summary: 'As it’s time to return to school, the Health and Human Services Administration for Children and Families is helping parents and teachers prepare anytime, anywhere. Head Start Resources, an app available on iOS and Android, is a gateway to tools and resources for those associated' authors: - katie-steffy topics: - mobile - HHS - mobile-apps - mobile-gov - mobile-gov-community-of-practice - thursday-mobile-products - united-states-department-of-health-and-human-services --- {{< legacy-img src="2014/08/250-x-444-HHS-Head-Start-App.jpg" alt="250 x 444 HHS Head Start App" >}}As it’s time to return to school, the [Health and Human Services Administration for Children and Families](https://www.acf.hhs.gov/) is helping parents and teachers prepare anytime, anywhere. Head Start Resources, an app available on [iOS](http://hsicc.cmail2.com/t/j-l-idtufd-kluyyuljt-q/) and [Android](http://hsicc.cmail2.com/t/j-l-idtufd-kluyyuljt-n/), is a gateway to tools and resources for those associated with or interested in the program. With the app, users can access: * The latest and greatest in Head Start News and updates, * The nearest Head Start locations with a map feature that utilizes geolocation, * Links to their website via a search function, with resources pertaining to Performance Standards and information about the Head Start Act, and * Help by utilizing the “Contact Us” section, featuring a phone number, email, office hours, and an interactive form. Head Start Resources has implemented numerous tools that we [mentioned last week]({{< ref "2014-07-30-customization-is-key-to-better-mobile-user-experience.md" >}}) to fit their users’ needs. Want to learn how your agency can get started with a mobile product that users rave about? Join the [MobileGov Community of Practice]({{< ref "mobilegov.md" >}}) today and see what other agencies are doing by checking out the [USA.gov Apps Registry](http://apps.usa.gov/register).

79.296296

586

0.760859

eng_Latn

0.977023

e9421d1ace63c5140b979d949ecd440a6c347ada

48,405

md

Markdown

_listings/aws-ec2-systems-manager/actionputinventory-get-postman.md

streamdata-gallery-organizations/aws-ec2-systems-manager

ec26059a626ce0aa3aa40752addd3b48dcd89cd1

[ "CC-BY-3.0" ]

null

_listings/aws-ec2-systems-manager/actionputinventory-get-postman.md

streamdata-gallery-organizations/aws-ec2-systems-manager

ec26059a626ce0aa3aa40752addd3b48dcd89cd1

[ "CC-BY-3.0" ]

null

_listings/aws-ec2-systems-manager/actionputinventory-get-postman.md

streamdata-gallery-organizations/aws-ec2-systems-manager

ec26059a626ce0aa3aa40752addd3b48dcd89cd1

[ "CC-BY-3.0" ]

null

{ "info": { "name": "Amazon EC2 Systems Manager API Put Inventory", "_postman_id": "218ca574-2189-41a7-9c69-aa7eccc52ab5", "description": "Bulk update custom inventory items on one more instance.", "schema": "https://schema.getpostman.com/json/collection/v2.0.0/" }, "item": [ { "name": "Resources", "item": [ { "id": "4a6cc21d-b305-47c7-b70a-eb0bb862c9fc", "name": "addTagsToResource", "request": { "url": "http://example.com/api/?Action=AddTagsToResource?ResourceId=ResourceId&ResourceType=ResourceType&Tags=Tags", "method": "GET", "body": { "mode": "raw" }, "description": "Adds or overwrites one or more tags for the specified resource." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "46613a2d-d76a-414c-a1eb-906fe1a410de" } ] } ] }, { "name": "Cancel", "item": [ { "id": "cca4bb39-c89f-489c-a0c8-c31b653f5540", "name": "cancelCommand", "request": { "url": "http://example.com/api/?Action=CancelCommand?CommandId=CommandId&InstanceIds=InstanceIds", "method": "GET", "body": { "mode": "raw" }, "description": "Attempts to cancel the command specified by the Command ID." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "9a53f3c6-3182-4e82-af75-f3a7cc16abd9" } ] } ] }, { "name": "Activation", "item": [ { "id": "a9195b3d-8098-418c-b36d-73ab08760ba3", "name": "createActivation", "request": { "url": "http://example.com/api/?Action=CreateActivation?DefaultInstanceName=DefaultInstanceName&Description=Description&ExpirationDate=ExpirationDate&IamRole=IamRole&RegistrationLimit=RegistrationLimit", "method": "GET", "body": { "mode": "raw" }, "description": "Registers your on-premises server or virtual machine with Amazon EC2 so that you can manage\n these resources using Run Command." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "2235050f-3903-475c-a63d-c08c165461a1" } ] }, { "id": "b9c316b6-30a1-4095-b96e-91654c7d3b16", "name": "deleteActivation", "request": { "url": "http://example.com/api/?Action=DeleteActivation?ActivationId=ActivationId", "method": "GET", "body": { "mode": "raw" }, "description": "Deletes an activation." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "b15f47c8-58c0-4e17-8cce-fa6904feb0fb" } ] } ] }, { "name": "Association", "item": [ { "id": "cc263512-9b92-43a6-9c48-f39444f6fbb5", "name": "createAssociation", "request": { "url": "http://example.com/api/?Action=CreateAssociation?DocumentVersion=DocumentVersion&InstanceId=InstanceId&Name=Name&OutputLocation=OutputLocation&Parameters=Parameters&ScheduleExpression=ScheduleExpression&Targets=Targets", "method": "GET", "body": { "mode": "raw" }, "description": "Associates the specified SSM document with the specified instances or targets." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "94ac6841-5c0a-4139-b55e-100176b2e8f9" } ] }, { "id": "b66d9569-0f35-4877-8cc4-99a857966e1d", "name": "createAssociationBatch", "request": { "url": "http://example.com/api/?Action=CreateAssociationBatch?Entries=Entries", "method": "GET", "body": { "mode": "raw" }, "description": "Associates the specified SSM document with the specified instances or targets." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "cdb14290-62f2-4e30-95ab-0199bed1ad4b" } ] }, { "id": "7c9c80b7-e5bc-4107-9455-2a0e6c61aaa8", "name": "deleteAssociation", "request": { "url": "http://example.com/api/?Action=DeleteAssociation?AssociationId=AssociationId&InstanceId=InstanceId&Name=Name", "method": "GET", "body": { "mode": "raw" }, "description": "Disassociates the specified SSM document from the specified instance." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "62640dbd-9a55-499a-8ba8-d0fb9f2bbc73" } ] }, { "id": "2b662ad1-8b87-43f5-bb8e-575063d2c773", "name": "describeAssociation", "request": { "url": "http://example.com/api/?Action=DescribeAssociation?AssociationId=AssociationId&InstanceId=InstanceId&Name=Name", "method": "GET", "body": { "mode": "raw" }, "description": "Describes the associations for the specified SSM document or instance." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "73ab7498-3d70-4e6d-aaa5-0c852bfa288f" } ] } ] }, { "name": "Document", "item": [ { "id": "67872a5a-21bf-4f85-9c97-9b5117d64e56", "name": "createDocument", "request": { "url": "http://example.com/api/?Action=CreateDocument?Content=Content&DocumentType=DocumentType&Name=Name", "method": "GET", "body": { "mode": "raw" }, "description": "Creates an SSM document." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "2ebb6dea-5386-4ee7-919e-0a841cbaf71f" } ] }, { "id": "aff76b09-ba34-4a45-b280-c53d9f53b93d", "name": "deleteDocument", "request": { "url": "http://example.com/api/?Action=DeleteDocument?Name=Name", "method": "GET", "body": { "mode": "raw" }, "description": "Deletes the SSM document and all instance associations to the document." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "ae3c9ead-418e-4b89-90ea-f8c783532ffd" } ] }, { "id": "7639550a-a33e-46c5-b1f9-53de6d4623a8", "name": "describeDocument", "request": { "url": "http://example.com/api/?Action=DescribeDocument?DocumentVersion=DocumentVersion&Name=Name", "method": "GET", "body": { "mode": "raw" }, "description": "Describes the specified SSM document." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "680fe4b5-2257-49f7-9401-8dd351e480a0" } ] }, { "id": "0f2ca581-81dd-4744-8d10-a8f863fa03ae", "name": "describeDocumentPermission", "request": { "url": "http://example.com/api/?Action=DescribeDocumentPermission?Name=Name&PermissionType=PermissionType", "method": "GET", "body": { "mode": "raw" }, "description": "Describes the permissions for an SSM document." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "8f7ba10c-e411-4393-8116-41a119b8ea03" } ] }, { "id": "138a2fdf-0bd2-48ba-868a-ba526a2cab07", "name": "getDocument", "request": { "url": "http://example.com/api/?Action=GetDocument?DocumentVersion=DocumentVersion&Name=Name", "method": "GET", "body": { "mode": "raw" }, "description": "Gets the contents of the specified SSM document." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "1cd93416-db6f-42c6-97fb-5a321f813a34" } ] } ] }, { "name": "Maintenance", "item": [ { "id": "22ca09ca-11f9-4f8b-96ad-98075ace0edf", "name": "createMaintenanceWindow", "request": { "url": "http://example.com/api/?Action=CreateMaintenanceWindow?AllowUnassociatedTargets=AllowUnassociatedTargets&ClientToken=ClientToken&Cutoff=Cutoff&Duration=Duration&Name=Name&Schedule=Schedule", "method": "GET", "body": { "mode": "raw" }, "description": "Creates a new Maintenance Window." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "fdbaefeb-df89-42da-ac0b-f44bae193079" } ] }, { "id": "a62bae82-9c34-4c82-8da4-cba35aadd76b", "name": "deleteMaintenanceWindow", "request": { "url": "http://example.com/api/?Action=DeleteMaintenanceWindow?WindowId=WindowId", "method": "GET", "body": { "mode": "raw" }, "description": "Deletes a Maintenance Window." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "c91097e1-84a6-4581-b382-49b8246ec805" } ] }, { "id": "73f3253b-55a2-438a-a54a-7b0e332a5800", "name": "describeMaintenanceWindowExecutions", "request": { "url": "http://example.com/api/?Action=DescribeMaintenanceWindowExecutions?Filters=Filters&MaxResults=MaxResults&NextToken=NextToken&WindowId=WindowId", "method": "GET", "body": { "mode": "raw" }, "description": "Lists the executions of a Maintenance Window (meaning, information about when the\n Maintenance Window was scheduled to be active and information about tasks registered and run with\n the Maintenance Window)." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "d3d93dab-ae02-4681-8233-4fb31c16c18e" } ] }, { "id": "875003cc-d5a3-474f-85cd-ff538c1debd9", "name": "describeMaintenanceWindowExecutionTaskInvocations", "request": { "url": "http://example.com/api/?Action=DescribeMaintenanceWindowExecutionTaskInvocations?Filters=Filters&MaxResults=MaxResults&NextToken=NextToken&TaskId=TaskId&WindowExecutionId=WindowExecutionId", "method": "GET", "body": { "mode": "raw" }, "description": "Retrieves the individual task executions (one per target) for a particular task executed\n as part of a Maintenance Window execution." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "d562c874-69c5-4881-814b-2b04dc72db6c" } ] }, { "id": "7a96223a-93b8-41b2-aa68-14cce5b4ef8c", "name": "describeMaintenanceWindowExecutionTasks", "request": { "url": "http://example.com/api/?Action=DescribeMaintenanceWindowExecutionTasks?Filters=Filters&MaxResults=MaxResults&NextToken=NextToken&WindowExecutionId=WindowExecutionId", "method": "GET", "body": { "mode": "raw" }, "description": "For a given Maintenance Window execution, lists the tasks that were executed." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "7cb428b3-3509-4c49-ae7b-eb49f989a11e" } ] }, { "id": "c726a80b-5518-4bc7-9149-058f35698729", "name": "describeMaintenanceWindows", "request": { "url": "http://example.com/api/?Action=DescribeMaintenanceWindows?Filters=Filters&MaxResults=MaxResults&NextToken=NextToken", "method": "GET", "body": { "mode": "raw" }, "description": "Retrieves the Maintenance Windows in an AWS account." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "3de4d6fe-2b88-4b2d-a140-39703ddfe8d3" } ] }, { "id": "22b1f60b-d7ba-484b-be2d-cc2a1a598dd9", "name": "describeMaintenanceWindowTargets", "request": { "url": "http://example.com/api/?Action=DescribeMaintenanceWindowTargets?Filters=Filters&MaxResults=MaxResults&NextToken=NextToken&WindowId=WindowId", "method": "GET", "body": { "mode": "raw" }, "description": "Lists the targets registered with the Maintenance Window." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "936d9ee1-3fbf-48c0-8f19-b87791057317" } ] }, { "id": "ec419efe-6823-49bc-a183-adde34cc9f02", "name": "describeMaintenanceWindowTasks", "request": { "url": "http://example.com/api/?Action=DescribeMaintenanceWindowTasks?Filters=Filters&MaxResults=MaxResults&NextToken=NextToken&WindowId=WindowId", "method": "GET", "body": { "mode": "raw" }, "description": "Lists the tasks in a Maintenance Window." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "dea96027-2095-43ce-b91d-e2b1b14ceeec" } ] }, { "id": "8065b2c0-10f4-4753-b360-8f728e57c1d9", "name": "getMaintenanceWindow", "request": { "url": "http://example.com/api/?Action=GetMaintenanceWindow?WindowId=WindowId", "method": "GET", "body": { "mode": "raw" }, "description": "Retrieves a Maintenance Window." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "4e74cda9-6a4a-436d-ade0-eeafbe1a36c1" } ] }, { "id": "e27ab909-3947-4fc0-a14a-bcbd260245b9", "name": "getMaintenanceWindowExecution", "request": { "url": "http://example.com/api/?Action=GetMaintenanceWindowExecution?WindowExecutionId=WindowExecutionId", "method": "GET", "body": { "mode": "raw" }, "description": "Retrieves details about a specific task executed as part of a Maintenance Window\n execution." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "904f01ae-7127-494f-a8aa-b4b65a06c59c" } ] }, { "id": "132eed8d-78f2-4c31-a28a-142014861b13", "name": "getMaintenanceWindowExecutionTask", "request": { "url": "http://example.com/api/?Action=GetMaintenanceWindowExecutionTask?TaskId=TaskId&WindowExecutionId=WindowExecutionId", "method": "GET", "body": { "mode": "raw" }, "description": "Retrieves the details about a specific task executed as part of a Maintenance Window\n execution." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "c2cf68f4-ff93-4376-b9cf-e27324cb5c02" } ] } ] }, { "name": "Baseline", "item": [ { "id": "1c0735c0-6f07-4d9c-9f0e-4eab757bb8d1", "name": "createPatchBaseline", "request": { "url": "http://example.com/api/?Action=CreatePatchBaseline?ApprovalRules=ApprovalRules&ApprovedPatches=ApprovedPatches&ClientToken=ClientToken&Description=Description&GlobalFilters=GlobalFilters&Name=Name&RejectedPatches=RejectedPatches", "method": "GET", "body": { "mode": "raw" }, "description": "Creates a patch baseline." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "66483797-cc9c-4a3c-8f68-f780e66cf362" } ] }, { "id": "d2f74972-f2fd-4f41-869b-058aa6e3fbc8", "name": "deletePatchBaseline", "request": { "url": "http://example.com/api/?Action=DeletePatchBaseline?BaselineId=BaselineId", "method": "GET", "body": { "mode": "raw" }, "description": "Deletes a patch baseline." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "89cbec76-9503-4352-89c6-a96cdb883ad5" } ] }, { "id": "f04dff10-fe8e-4cd2-974d-118df3efe9db", "name": "getPatchBaseline", "request": { "url": "http://example.com/api/?Action=GetPatchBaseline?BaselineId=BaselineId", "method": "GET", "body": { "mode": "raw" }, "description": "Retrieves information about a patch baseline." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "b7ee16bd-808a-4600-aaf1-64d33ac88c7c" } ] } ] }, { "name": "Parameter", "item": [ { "id": "db5eff41-1f2e-4e00-863f-4d72e8a82a84", "name": "deleteParameter", "request": { "url": "http://example.com/api/?Action=DeleteParameter?Name=Name", "method": "GET", "body": { "mode": "raw" }, "description": "Delete a parameter from the system." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "f25e0309-3385-407c-b458-33ea571dcfc9" } ] }, { "id": "2c154c53-9261-4332-81d1-d9c97bc6adf3", "name": "getParameterHistory", "request": { "url": "http://example.com/api/?Action=GetParameterHistory?MaxResults=MaxResults&Name=Name&NextToken=NextToken&WithDecryption=WithDecryption", "method": "GET", "body": { "mode": "raw" }, "description": "Query a list of all parameters used by the AWS account." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "6d1c9d83-1969-46d1-8ce5-08c392f9a8a3" } ] } ] }, { "name": "Deregister", "item": [ { "id": "b8eec606-d006-4882-b605-52a2dbb34ee7", "name": "deregisterManagedInstance", "request": { "url": "http://example.com/api/?Action=DeregisterManagedInstance?InstanceId=InstanceId", "method": "GET", "body": { "mode": "raw" }, "description": "Removes the server or virtual machine from the list of registered servers." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "809986ba-860c-452c-8e92-a33ed54297f7" } ] }, { "id": "4b052e9e-3ab0-452f-83d4-f6542400a21a", "name": "deregisterPatchBaselineForPatchGroup", "request": { "url": "http://example.com/api/?Action=DeregisterPatchBaselineForPatchGroup?BaselineId=BaselineId&PatchGroup=PatchGroup", "method": "GET", "body": { "mode": "raw" }, "description": "Removes a patch group from a patch baseline." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "b3263660-9391-4194-8c90-4c1871137f6d" } ] }, { "id": "9ffb3a5b-3907-4eb4-a504-3fbaac2a6ab0", "name": "deregisterTargetFromMaintenanceWindow", "request": { "url": "http://example.com/api/?Action=DeregisterTargetFromMaintenanceWindow?WindowId=WindowId&WindowTargetId=WindowTargetId", "method": "GET", "body": { "mode": "raw" }, "description": "Removes a target from a Maintenance Window." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "2937eee2-5c5e-413e-bb35-621bdf18632c" } ] }, { "id": "7893d947-8012-477e-b2d7-bf32cd336bb8", "name": "deregisterTaskFromMaintenanceWindow", "request": { "url": "http://example.com/api/?Action=DeregisterTaskFromMaintenanceWindow?WindowId=WindowId&WindowTaskId=WindowTaskId", "method": "GET", "body": { "mode": "raw" }, "description": "Removes a task from a Maintenance Window." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "7d1c8ce4-6143-4ddc-b07e-0d8355e9830a" } ] } ] }, { "name": "Activations", "item": [ { "id": "2059f19d-b739-4149-8e83-178d209e765a", "name": "describeActivations", "request": { "url": "http://example.com/api/?Action=DescribeActivations?Filters=Filters&MaxResults=MaxResults&NextToken=NextToken", "method": "GET", "body": { "mode": "raw" }, "description": "Details about the activation, including: the date and time the activation was created,\n the expiration date, the IAM role assigned to the instances in the activation, and the number of\n instances activated by this registration." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "861a96d1-c860-4fbf-899b-8ad79db41682" } ] } ] }, { "name": "Automation", "item": [ { "id": "b14cee34-4644-4933-b105-8aa4eeab1c12", "name": "describeAutomationExecutions", "request": { "url": "http://example.com/api/?Action=DescribeAutomationExecutions?Filters=Filters&MaxResults=MaxResults&NextToken=NextToken", "method": "GET", "body": { "mode": "raw" }, "description": "Provides details about all active and terminated Automation executions." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "d983555c-6d3e-40e2-963b-b3ae41a3bbad" } ] }, { "id": "bb893dd1-c5b7-4064-8920-554335c4c841", "name": "getAutomationExecution", "request": { "url": "http://example.com/api/?Action=GetAutomationExecution?AutomationExecutionId=AutomationExecutionId", "method": "GET", "body": { "mode": "raw" }, "description": "Get detailed information about a particular Automation execution." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "0b6d0698-e280-4e1f-82fb-d882ef2abca7" } ] } ] }, { "name": "Available", "item": [ { "id": "820d749e-f828-4ffb-8c5a-4426c31d8abe", "name": "describeAvailablePatches", "request": { "url": "http://example.com/api/?Action=DescribeAvailablePatches?Filters=Filters&MaxResults=MaxResults&NextToken=NextToken", "method": "GET", "body": { "mode": "raw" }, "description": "Lists all patches that could possibly be included in a patch baseline." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "e298df6c-ea0c-4d76-8067-ef91d82e6cbf" } ] } ] }, { "name": "Effective", "item": [ { "id": "8e0823c3-c6b3-4576-a56f-f39e5bfe3235", "name": "describeEffectiveInstanceAssociations", "request": { "url": "http://example.com/api/?Action=DescribeEffectiveInstanceAssociations?InstanceId=InstanceId&MaxResults=MaxResults&NextToken=NextToken", "method": "GET", "body": { "mode": "raw" }, "description": "All associations for the instance(s)." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "7e2c1d90-16b9-4fd1-8aed-6e9fc89b054a" } ] }, { "id": "dfd6c2ab-f08d-400b-85f9-b6ad15f48834", "name": "describeEffectivePatchesForPatchBaseline", "request": { "url": "http://example.com/api/?Action=DescribeEffectivePatchesForPatchBaseline?BaselineId=BaselineId&MaxResults=MaxResults&NextToken=NextToken", "method": "GET", "body": { "mode": "raw" }, "description": "Retrieves the current effective patches (the patch and the approval state) for the specified patch baseline." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "320bde45-7fa0-49bf-ad42-5854f0dcaaa6" } ] } ] }, { "name": "Instance", "item": [ { "id": "e94166f8-654f-48b9-ad80-0584c53c623d", "name": "describeInstanceAssociationsStatus", "request": { "url": "http://example.com/api/?Action=DescribeInstanceAssociationsStatus?InstanceId=InstanceId&MaxResults=MaxResults&NextToken=NextToken", "method": "GET", "body": { "mode": "raw" }, "description": "The status of the associations for the instance(s)." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "29563fea-e00c-4aad-a895-67f6e7f4d0a3" } ] }, { "id": "ff29bf88-e014-42a1-a5f8-1fac67bed2ed", "name": "describeInstanceInformation", "request": { "url": "http://example.com/api/?Action=DescribeInstanceInformation?Filters=Filters&InstanceInformationFilterList=InstanceInformationFilterList&MaxResults=MaxResults&NextToken=NextToken", "method": "GET", "body": { "mode": "raw" }, "description": "Describes one or more of your instances." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "1938814c-7508-4261-a100-8b903b56b89a" } ] }, { "id": "42307c60-084a-433e-9bd1-6036f5c22251", "name": "describeInstancePatches", "request": { "url": "http://example.com/api/?Action=DescribeInstancePatches?Filters=Filters&InstanceId=InstanceId&MaxResults=MaxResults&NextToken=NextToken", "method": "GET", "body": { "mode": "raw" }, "description": "Retrieves information about the patches on the specified instance and their state relative to the patch baseline being used for the instance." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "146f447b-4835-4a95-9cf8-9e923ae63bc7" } ] }, { "id": "491da069-0a3c-495b-903e-d99dcc808d3b", "name": "describeInstancePatchStates", "request": { "url": "http://example.com/api/?Action=DescribeInstancePatchStates?InstanceIds=InstanceIds&MaxResults=MaxResults&NextToken=NextToken", "method": "GET", "body": { "mode": "raw" }, "description": "Retrieves the high-level patch state of one or more instances." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "2a105b33-230c-4316-a1cf-400f9f044c50" } ] }, { "id": "b92f7ff5-2521-4a5d-bbc5-5a22e0990743", "name": "describeInstancePatchStatesForPatchGroup", "request": { "url": "http://example.com/api/?Action=DescribeInstancePatchStatesForPatchGroup?Filters=Filters&MaxResults=MaxResults&NextToken=NextToken&PatchGroup=PatchGroup", "method": "GET", "body": { "mode": "raw" }, "description": "Retrieves the high-level patch state for the instances in the specified patch group." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "628f838b-85cf-423b-904a-bc4ba9720a2c" } ] } ] }, { "name": "Parameters", "item": [ { "id": "7bbef104-5860-4860-90ef-55adcf915bc4", "name": "describeParameters", "request": { "url": "http://example.com/api/?Action=DescribeParameters?Filters=Filters&MaxResults=MaxResults&NextToken=NextToken", "method": "GET", "body": { "mode": "raw" }, "description": "Get information about a parameter." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "5d185a88-f81b-4f09-a48c-0442e907e3a0" } ] }, { "id": "0ae4de65-66eb-4126-8307-4bb46993d450", "name": "getParameters", "request": { "url": "http://example.com/api/?Action=GetParameters?Names=Names&WithDecryption=WithDecryption", "method": "GET", "body": { "mode": "raw" }, "description": "Get a list of parameters used by the AWS account." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "9e928530-f767-48dc-b136-0cd0b5ca64be" } ] } ] }, { "name": "Baselines", "item": [ { "id": "48547381-609c-4593-8d5f-64e569d37364", "name": "describePatchBaselines", "request": { "url": "http://example.com/api/?Action=DescribePatchBaselines?Filters=Filters&MaxResults=MaxResults&NextToken=NextToken", "method": "GET", "body": { "mode": "raw" }, "description": "Lists the patch baselines in your AWS account." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "3d492f93-a0a3-440f-80f7-39b69190a1a7" } ] } ] }, { "name": "Groups", "item": [ { "id": "da83b93f-f454-4545-9549-7dd40993c04a", "name": "describePatchGroups", "request": { "url": "http://example.com/api/?Action=DescribePatchGroups?MaxResults=MaxResults&NextToken=NextToken", "method": "GET", "body": { "mode": "raw" }, "description": "Lists all patch groups that have been registered with patch baselines." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "ba422cb9-a07d-4519-9aa6-ad4bf27ea9cd" } ] } ] }, { "name": "Group", "item": [ { "id": "b0f14d29-59d1-4990-967d-33f9bd60a362", "name": "describePatchGroupState", "request": { "url": "http://example.com/api/?Action=DescribePatchGroupState?PatchGroup=PatchGroup", "method": "GET", "body": { "mode": "raw" }, "description": "Returns high-level aggregated patch compliance state for a patch group." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "934b629c-3867-412a-b270-89801af57811" } ] } ] }, { "name": "Command", "item": [ { "id": "7c9527f2-b549-4cff-863a-a81fa9bb8fd8", "name": "getCommandInvocation", "request": { "url": "http://example.com/api/?Action=GetCommandInvocation?CommandId=CommandId&InstanceId=InstanceId&PluginName=PluginName", "method": "GET", "body": { "mode": "raw" }, "description": "Returns detailed information about command execution for an invocation or plugin." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "ca25ceb1-5e14-4b25-85a0-684cfeb7de5f" } ] } ] }, { "name": "Default", "item": [ { "id": "4c83f168-68ea-4540-95e5-f6240fe4b54b", "name": "getDefaultPatchBaseline", "request": { "url": "http://example.com/api/?Action=GetDefaultPatchBaseline?BaselineId=BaselineId", "method": "GET", "body": { "mode": "raw" }, "description": "Retrieves the default patch baseline." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "f3394600-144b-420a-8359-ce68b4923350" } ] } ] }, { "name": "Deployable", "item": [ { "id": "c2c0153e-34da-4b6a-9ca2-662ed60eff71", "name": "getDeployablePatchSnapshotForInstance", "request": { "url": "http://example.com/api/?Action=GetDeployablePatchSnapshotForInstance?InstanceId=InstanceId&SnapshotId=SnapshotId", "method": "GET", "body": { "mode": "raw" }, "description": "Retrieves the current snapshot for the patch baseline the instance uses." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "4e573e7a-3cf0-4dbf-9bdc-a35119b7c42c" } ] } ] }, { "name": "Inventory", "item": [ { "id": "0ff788d5-16f5-43ba-8d31-55c593482b8a", "name": "getInventory", "request": { "url": "http://example.com/api/?Action=GetInventory?Filters=Filters&MaxResults=MaxResults&NextToken=NextToken&ResultAttributes=ResultAttributes", "method": "GET", "body": { "mode": "raw" }, "description": "Query inventory information." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "1bdd336b-d121-44da-b5a8-d23c9d006b54" } ] }, { "id": "61e37ed2-afb8-4860-a887-b6a1970dd518", "name": "getInventorySchema", "request": { "url": "http://example.com/api/?Action=GetInventorySchema?MaxResults=MaxResults&NextToken=NextToken&TypeName=TypeName", "method": "GET", "body": { "mode": "raw" }, "description": "Return a list of inventory type names for the account, or return a list of attribute\n names for a specific Inventory item type." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "49e3ba23-f210-4867-9fbe-52238cd981b0" } ] }, { "id": "31b45811-3053-45c4-a653-32ae2fad7f19", "name": "putInventory", "request": { "url": "http://example.com/api/?Action=PutInventory?InstanceId=InstanceId&Items=Items", "method": "GET", "body": { "mode": "raw" }, "description": "Bulk update custom inventory items on one more instance." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "de544fa3-89f9-47e6-8729-b358a99d9c8a" } ] } ] }, { "name": "BaselineGroup", "item": [ { "id": "a4cf1564-9046-4bb0-b966-7facf048de91", "name": "getPatchBaselineForPatchGroup", "request": { "url": "http://example.com/api/?Action=GetPatchBaselineForPatchGroup?PatchGroup=PatchGroup", "method": "GET", "body": { "mode": "raw" }, "description": "Retrieves the patch baseline that should be used for the specified patch group." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "5563b87d-824a-4ea6-b01f-072e3b674ab1" } ] } ] }, { "name": "List", "item": [ { "id": "85e47b46-9ea0-45e2-ac60-71ff428199cb", "name": "listAssociations", "request": { "url": "http://example.com/api/?Action=ListAssociations?AssociationFilterList=AssociationFilterList&MaxResults=MaxResults&NextToken=NextToken", "method": "GET", "body": { "mode": "raw" }, "description": "Lists the associations for the specified SSM document or instance." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "1b2f8d81-78fe-451f-9ec7-d1487051dc59" } ] }, { "id": "527bae11-0c17-4f16-9d71-b7c2f1e3b5a3", "name": "listCommandInvocations", "request": { "url": "http://example.com/api/?Action=ListCommandInvocations?CommandId=CommandId&Details=Details&Filters=Filters&InstanceId=InstanceId&MaxResults=MaxResults&NextToken=NextToken", "method": "GET", "body": { "mode": "raw" }, "description": "An invocation is copy of a command sent to a specific instance." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "30c59892-2bfe-41e6-a697-c5b4169c632e" } ] }, { "id": "c8225664-79df-4ae0-90e9-e39741e44c77", "name": "listCommands", "request": { "url": "http://example.com/api/?Action=ListCommands?CommandId=CommandId&Filters=Filters&InstanceId=InstanceId&MaxResults=MaxResults&NextToken=NextToken", "method": "GET", "body": { "mode": "raw" }, "description": "Lists the commands requested by users of the AWS account." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "9fdb8766-6eaa-4576-a6b6-ef01a783b744" } ] }, { "id": "2626f86c-3e1b-4f83-af50-61f1696ea51c", "name": "listDocuments", "request": { "url": "http://example.com/api/?Action=ListDocuments?DocumentFilterList=DocumentFilterList&MaxResults=MaxResults&NextToken=NextToken", "method": "GET", "body": { "mode": "raw" }, "description": "Describes one or more of your SSM documents." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "462766bb-2730-4d49-a448-3e85bc04a2a0" } ] }, { "id": "dd0f354c-72e5-4bed-b3ef-21c2aff55587", "name": "listDocumentVersions", "request": { "url": "http://example.com/api/?Action=ListDocumentVersions?MaxResults=MaxResults&Name=Name&NextToken=NextToken", "method": "GET", "body": { "mode": "raw" }, "description": "List all versions for a document." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "d7c9f04e-e81e-437f-bb56-6746088e4d4b" } ] }, { "id": "aecade29-687d-4a46-b31e-394b720d0d13", "name": "listInventoryEntries", "request": { "url": "http://example.com/api/?Action=ListInventoryEntries?Filters=Filters&InstanceId=InstanceId&MaxResults=MaxResults&NextToken=NextToken&TypeName=TypeName", "method": "GET", "body": { "mode": "raw" }, "description": "A list of inventory items returned by the request." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "3a8a0705-093b-4382-9903-bfd87dc29826" } ] }, { "id": "1a91bf47-e029-4143-9d71-257cacacc14b", "name": "listTagsForResource", "request": { "url": "http://example.com/api/?Action=ListTagsForResource?ResourceId=ResourceId&ResourceType=ResourceType", "method": "GET", "body": { "mode": "raw" }, "description": "Returns a list of the tags assigned to the specified resource." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "560630af-228e-4d37-a24a-14e3eb0c4072" } ] } ] }, { "name": "Modify", "item": [ { "id": "3e5dca55-e877-49d7-b2c4-123aedaed5b5", "name": "modifyDocumentPermission", "request": { "url": "http://example.com/api/?Action=ModifyDocumentPermission?AccountIdsToAdd=AccountIdsToAdd&AccountIdsToRemove=AccountIdsToRemove&Name=Name&PermissionType=PermissionType", "method": "GET", "body": { "mode": "raw" }, "description": "Share a document publicly or privately." }, "response": [ { "status": "OK", "code": 200, "name": "Response_200", "id": "04494a24-b1bc-4cd3-933a-3d73674b44bb" } ] } ] } ] }

34.208481

263

0.452226

yue_Hant

0.523712

e9424979dcb8f5ac38163fbbc740147f8dcc21aa

4,139

md

Markdown

windows-driver-docs-pr/network/ndis-status-wwan-home-provider.md

AmadeusW/windows-driver-docs

6d272f80814969bbb5ec836cbbebdf5cae52ee35

[ "CC-BY-4.0", "MIT" ]

4

2017-05-30T18:13:16.000Z

2021-09-26T19:45:08.000Z

windows-driver-docs-pr/network/ndis-status-wwan-home-provider.md

AmadeusW/windows-driver-docs

6d272f80814969bbb5ec836cbbebdf5cae52ee35

[ "CC-BY-4.0", "MIT" ]

null

windows-driver-docs-pr/network/ndis-status-wwan-home-provider.md

AmadeusW/windows-driver-docs

6d272f80814969bbb5ec836cbbebdf5cae52ee35

[ "CC-BY-4.0", "MIT" ]

1

2021-09-26T19:45:46.000Z

--- title: NDIS_STATUS_WWAN_HOME_PROVIDER author: windows-driver-content description: Miniport drivers use the NDIS_STATUS_WWAN_HOME_PROVIDER notification to inform the MB Service about the completion of OID_WWAN_HOME_PROVIDER \ 160; query requests. ms.assetid: a5733c62-be4e-4f86-9639-6addd31baf0c ms.author: windowsdriverdev ms.date: 08/08/2017 ms.topic: article ms.prod: windows-hardware ms.technology: windows-devices keywords: -NDIS_STATUS_WWAN_HOME_PROVIDER Network Drivers Starting with Windows Vista --- # NDIS\_STATUS\_WWAN\_HOME\_PROVIDER Miniport drivers use the NDIS\_STATUS\_WWAN\_HOME\_PROVIDER notification to inform the MB Service about the completion of [OID\_WWAN\_HOME\_PROVIDER](oid-wwan-home-provider.md) query requests. Miniport drivers cannot use this notification to send unsolicited events. This notification uses the [**NDIS\_WWAN\_HOME\_PROVIDER**](https://msdn.microsoft.com/library/windows/hardware/ff567909) structure. Remarks ------- Miniport drivers must comply with the following rules when responding to OID\_WWAN\_HOME\_PROVIDER query requests: - GSM-Based Devices: The home provider name can be retrieved from the Subscriber Identity Module (SIM) using several methods, such as from the EFSPN elementary file in the SIM (EFSPN is defined in the 3GPP TS 31.102 under section Service Provider Name), or from the operator-specific extensions when the EFSPN is not provisioned. You should refer to the operator-specific requirements specifications for obtaining the home provider name, extracting MCC-MNC from IMSI, and performing a look up in the GSMA SE.13 database. Contact the operator when retrieving operator-specific home provider names if the EFSPN is not provisioned. If a SIM is not provisioned with a home provider name through EFSPN or any other mechanism, miniport drivers should set the provider name to **NULL**. For details about a SIM card's file system, see the 3GPP TS 11.11 specification. If the provider identification is not provisioned in the Subscriber Identity Module (SIM card), miniport drivers should return WWAN\_STATUS\_READ\_FAILURE. - CDMA-Based Devices: Returning the home provider name is mandatory. It is recommended that IHVs provide this information in their device as part of network personalization. If the provider identity is not available, miniport drivers for CDMA-based providers must set the **Provider.ProviderId** member of the NDIS\_WWAN\_HOME\_PROVIDER structure to WWAN\_CDMA\_DEFAULT\_PROVIDER\_ID. Miniport drivers must return this information when the device ready-state changes to **WwanReadyStateInitialized** and format all the members of the WWAN\_PROVIDER structure, as appropriate. Requirements ------------ <table> <colgroup> <col width="50%" /> <col width="50%" /> </colgroup> <tbody> <tr class="odd"> <td><p>Version</p></td> <td><p>Available in Windows 7 and later versions of Windows.</p></td> </tr> <tr class="even"> <td><p>Header</p></td> <td>Ndis.h</td> </tr> </tbody> </table> ## See also [OID\_WWAN\_HOME\_PROVIDER](oid-wwan-home-provider.md) [**NDIS\_WWAN\_HOME\_PROVIDER**](https://msdn.microsoft.com/library/windows/hardware/ff567909) -------------------- [Send comments about this topic to Microsoft](mailto:wsddocfb@microsoft.com?subject=Documentation%20feedback%20%5Bnetvista\netvista%5D:%20NDIS_STATUS_WWAN_HOME_PROVIDER%20%20RELEASE:%20%288/8/2017%29&body=%0A%0APRIVACY%20STATEMENT%0A%0AWe%20use%20your%20feedback%20to%20improve%20the%20documentation.%20We%20don't%20use%20your%20email%20address%20for%20any%20other%20purpose,%20and%20we'll%20remove%20your%20email%20address%20from%20our%20system%20after%20the%20issue%20that%20you're%20reporting%20is%20fixed.%20While%20we're%20working%20to%20fix%20this%20issue,%20we%20might%20send%20you%20an%20email%20message%20to%20ask%20for%20more%20info.%20Later,%20we%20might%20also%20send%20you%20an%20email%20message%20to%20let%20you%20know%20that%20we've%20addressed%20your%20feedback.%0A%0AFor%20more%20info%20about%20Microsoft's%20privacy%20policy,%20see%20http://privacy.microsoft.com/default.aspx. "Send comments about this topic to Microsoft")

56.69863

941

0.793428

eng_Latn

0.884587

e942b013025f54c9cb37f218d26cfbb08699c5f9

6,080

md

Markdown

notes/day05/readme.md

digitalideation/gencg_h2101

d82dad2e5011ee5e9db6a4a051e9b490665f0b94

[ "MIT" ]

1

2021-09-08T10:05:16.000Z

notes/day05/readme.md

digitalideation/gencg_h2101

d82dad2e5011ee5e9db6a4a051e9b490665f0b94

[ "MIT" ]

null

notes/day05/readme.md

digitalideation/gencg_h2101

d82dad2e5011ee5e9db6a4a051e9b490665f0b94

[ "MIT" ]

3

2021-09-29T11:28:57.000Z

2022-01-03T18:59:27.000Z

# Day 05 ## Schedule |Time |Desc | |--- |--- | |9:30 - 9:45 | Intro of the day | |9:45 - 10:00 | Sharing | |10:00 - 12:00 | Work on assignement | |12:00 - 13:00 | Lunch break :green_apple: | |13:00 - 15:00 | Work on assignement | ## :neutral_face: Face Generator ### Brief Create a program that is generating a parametric face. Your face should at least be controlled by 3 parameters but preferably more. Variations in some of the features can be used to control the expressiveness of the face or some other characteristics (species, gender, etc…) Differentiate continuous parameters (size and position of features) and discrete parameters (piercing, number of eyeballs). Consider the space you’re generating your face in (2D / 3D) and the view angle, front, profile, 3/4? [^note-id1] __You must first sketch your idea on paper before working with the software.__ ### Variations / Steps [^note-id1] - [ ] Bring your face to life - [ ] Try using real world data as input - [ ] Generate a collection (prints, cards) from your face collection ## Deliverables * Code and documentation of your process, add some live example + gifs / images. * Include a scan or photo of your drawings in the post ## More on Face Generator ### References !['Weird Faces - Matthias Dörfelt'](images/weird_faces.jpg) [_Weird Faces - Matthias Dörfelt_](https://www.creativeapplications.net/featured/weird-faces-study-by-matthias-dorfelt-using-paperjs/) Computer generated images have a certain aesthetics to them that make them immediately recognizable as such by the trained eye. Weird Faces is an attempt to combine my old interest in illustration with programing, to create something procedural that has a truly individual artistic touch to it and is not instantly recognizable as a generative art piece. Even though, the faces look hand-drawn, they are entirely expressed by algorithmic rules. Each face is random, each face is unique. Still, they look similar to my actual hand drawn faces. !['Strange Visions'](images/stranger_visions.jpg) [_Strange Visions - Heather Dewey-Hagborg_](https://deweyhagborg.com/projects/stranger-visions) In Stranger Visions Heather collected hairs, chewed up gum, and cigarette butts from the streets, public bathrooms and waiting rooms of New York City. She extracted DNA from them and analyzed it to computationally generate 3d printed life size full color portraits representing what those individuals might look like, based on genomic research. ![Lenny Face Generator](images/lenny.jpg) [_Lenny Face Generator_](https://lenny-face-generator.textsmilies.com/) ![Jabba](images/jabba.jpg) [_Pareidolia_](https://www.reddit.com/r/Pareidolia/) Pareidolia is the tendency for perception to impose a meaningful interpretation on a nebulous stimulus, usually visual, so that one sees an object, pattern, or meaning where there is none. ![Ig](images/ig.jpg) [_> source_](https://www.instagram.com/p/CUqCDq8Jpff/) !['Mas que la cara'](images/mas.jpg) [_Mas que la cara - Zach Lieberman_](https://zachlieberman.medium.com/m%C3%A1s-que-la-cara-overview-48331a0202c0) Mas que la Cara is a public art installation in Downtown Houston which augments participants faces with dynamically generated masks that respond to their movements. !['Face Trade'](images/face_trade.jpg) [_Face Trade - Matthias Dörfelt_](https://www.creativeapplications.net/c/face-trade-art-vending-machine-that-trades-mugshots-for-free-portraits/) Face Trade is an Art Vending Machine created by Matthias Dörfelt that dispenses unique prints of computer generated face drawings. Instead of paying with money, buyers trade a mugshot that is taken on the spot in order to be permanently stored in the Ethereum Blockchain, consequently turning the transaction into a semi-permanent Face Swap. !['Type Face'](images/typeface01.png) [_Type Face -Mary Huang_](http://www.creativeapplications.net/processing/typeface-processing/) Created by Mary Huang, TYPEFACE is a study of facial recognition and type design, creating a typeface that corresponds to each individual, like a typographic portrait. Somewhat similar to LAIKA project – interactive typeface, the challenge here were the limitations of geometric type system, being able to allow for a great amount of variation while maintaining a general level of quality in the letters. {% raw %} <iframe src="https://player.vimeo.com/video/69694262?h=edd986e6e2" width="640" height="360" frameborder="0" allow="autoplay; fullscreen; picture-in-picture" allowfullscreen></iframe> <p><a href="https://vimeo.com/69694262">Drawing faces instructed by facial recognition</a> from <a href="https://vimeo.com/user8828003">M Plummer-Fernandez</a> on <a href="https://vimeo.com">Vimeo</a>.</p> {% endraw %} !['Deep Privacy'](images/deep_privacy.gif) [_Deep Privacy - Hukkelas, Hakon and Mester, Rudolf and Lindseth, Frank_](https://github.com/hukkelas/DeepPrivacy) {% raw %} <iframe src="https://player.vimeo.com/video/29348533?h=5c0cc36b58&title=0&byline=0&portrait=0" width="640" height="360" frameborder="0" allow="autoplay; fullscreen; picture-in-picture" allowfullscreen></iframe> <p><a href="https://vimeo.com/29348533">Face Substitution</a> from <a href="https://vimeo.com/kylemcdonald">Kyle McDonald</a> on <a href="https://vimeo.com">Vimeo</a>.</p> {% endraw %} See also other [similar](https://www.creativeapplications.net/sound/faceshift-studio-experiments-by-kyle-mcdonald/) / [experiments](https://www.creativeapplications.net/openframeworks/scramble-suit-face-tracking-openframeworks/) by Kyle ### Example ![Ig](images/facemesh.jpg) [Mediapipe Facemesh in P5.js](https://editor.p5js.org/guma/sketches/IAlxLpyRd) [^note-id1]: [Code as Creative Medium - Tega Brain / Golan Levin](https://mitpress.mit.edu/books/code-creative-medium)

62.680412

542

0.73273

eng_Latn

0.945458

e942c7a4fbd6f54a9dd1b554f7020855eb96ef19

3,490

md

Markdown

source/_posts/spring-jpa-best-14.md

cheese10yun/Yun-Blog

c78f6562d06397b3544ba062149f9bc7fce13e8a

[ "Apache-2.0" ]

1

2017-10-13T12:59:08.000Z

source/_posts/spring-jpa-best-14.md

hanbong5938/hanbong5938.github.io

85d207bc5c52cb97f6cb9050ca14e89c3ec5a2b6

[ "Apache-2.0" ]

null

source/_posts/spring-jpa-best-14.md

hanbong5938/hanbong5938.github.io

85d207bc5c52cb97f6cb9050ca14e89c3ec5a2b6

[ "Apache-2.0" ]

5

2018-02-12T15:42:43.000Z

2020-03-08T12:12:02.000Z

--- layout: post title: Spring-JPA Best Practices step-14 - JUnit5 적용하기 subtitle: JUnit5 적용하기 catalog: true header-img: 'https://i.imgur.com/avC1Xor.jpg' tags: - Spring - Test - Guide date: 2019-02-06 21:15:00 thumbnail: --- > 해당 코드는 [Github](https://github.com/cheese10yun/spring-jpa-best-practices)를 확인해주세요. JUnit5는 다양한 어노테이션들이 추가되었습니다. 그중에 Junit5를 도입할 만큼 매력 있는 어노테이션 `@DisplayName` 입니다. 단순한 테스트 이외에는 테스트 코드 네이밍으로 테스트하고자 하는 의미를 전달하기가 매우 어렵습니다. 이때 아주 유용하게 사용할 수 있는 것이 `@DisplayName` 입니다. ![](https://github.com/cheese10yun/spring-jpa-best-practices/raw/master/images/junit5-display-name.png) 위 그림처럼 `@DisplayName(....)` 어노테이션으로 코드에 대한 설명을 문자열로 대체할 수 있습니다. 이 대체된 문자열은 실제 테스트 케이스 이름으로 표시됩니다. ## 의존성 추가 Spring Boot2의 테스트코드 의존성은 JUnit4를 기본으로 가져오기 때문에 `spring-boot-starter-test` 의존성 이외에도 추가적인 작업이 필요합니다. ```xml <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-test</artifactId> <scope>test</scope>  <exclusions> <exclusion> <groupId>junit</groupId> <artifactId>junit</artifactId> </exclusion> </exclusions> </dependency>  <dependency> <groupId>org.junit.jupiter</groupId> <artifactId>junit-jupiter-api</artifactId> <version>5.3.2</version> <scope>test</scope> </dependency> <dependency> <groupId>org.mockito</groupId> <artifactId>mockito-core</artifactId> <scope>test</scope> </dependency> <dependency> <groupId>org.mockito</groupId> <artifactId>mockito-junit-jupiter</artifactId> <scope>test</scope> </dependency> <dependency> <groupId>org.junit.platform</groupId> <artifactId>junit-platform-runner</artifactId> <version>1.2.0</version> <scope>test</scope> </dependency> <dependency> <groupId>org.junit.vintage</groupId> <artifactId>junit-vintage-engine</artifactId> <version>5.2.0</version> <scope>test</scope> </dependency> ``` ## 테스트 코드 ```java import org.junit.jupiter.api.DisplayName; import org.junit.jupiter.api.Test; import org.junit.jupiter.api.extension.ExtendWith; import org.junit.platform.runner.JUnitPlatform; import org.junit.runner.RunWith; import org.mockito.InjectMocks; import org.mockito.Mock; import org.mockito.junit.jupiter.MockitoExtension; import java.util.Optional; import static org.hamcrest.CoreMatchers.is; import static org.junit.Assert.assertThat; import static org.mockito.ArgumentMatchers.anyLong; import static org.mockito.BDDMockito.given; import static org.mockito.Mockito.atLeastOnce; import static org.mockito.Mockito.verify; @ExtendWith(MockitoExtension.class) public class AccountServiceJUnit5Test { @InjectMocks private AccountService accountService; @Mock private AccountRepository accountRepository; @Test @DisplayName("findById_존재하는경우_회원리턴") public void findBy_not_existed_test() { //given final AccountDto.SignUpReq dto = buildSignUpReq(); given(accountRepository.findById(anyLong())).willReturn(Optional.of(dto.toEntity())); //when final Account account = accountService.findById(anyLong()); //then verify(accountRepository, atLeastOnce()).findById(anyLong()); assertThatEqual(dto, account); } } ``` 필요한 패키지의 경로가 중요하기 때문에 필요한 `import`을 추가했습니다. 아직 Spring Boot2에서 기본으로 가져온 의존성이 아니기 때문에 복잡한 부분이 있습니다. Prod 코드에는 Spring Boot2에서 JUnit5를 기본으로 택했을 때 변경하는 것이 더 안전하고 효율적이라고 생각합니다.

27.265625

171

0.717192

kor_Hang

0.978167

e9441bb037fb5646baeaa733792b59acf8634a0a

957

md

Markdown

doc/301-400/326.IsPowerOfThree/README.md

Peefy/PeefyLeetCode

92156e4b48ba19e3f02e4286b9f733e9769a1dee

[ "Apache-2.0" ]

2

2018-05-03T07:50:03.000Z

2018-06-17T04:32:13.000Z

doc/301-400/326.IsPowerOfThree/README.md

Peefy/PeefyLeetCode

92156e4b48ba19e3f02e4286b9f733e9769a1dee

[ "Apache-2.0" ]

null

doc/301-400/326.IsPowerOfThree/README.md

Peefy/PeefyLeetCode

92156e4b48ba19e3f02e4286b9f733e9769a1dee

[ "Apache-2.0" ]

3

2018-11-09T14:18:11.000Z

2021-11-17T15:23:52.000Z

# problem 326 : IsPowerOfThree <img src="https://github.com/Peefy/PeefyLeetCode/blob/master/doc/301-400/326.IsPowerOfThree/problem.png"/> ## C++ Solution ```c++ class Solution { public: bool isPowerOfThree(int n) { if (n == 1) return true; if (n%3 != 0) return false; int i = 3; while (i < n) i *= 3; return i == n; } } ``` ## C# Solution ```csharp public class Solution { public bool IsPowerOfThree(int n) { if (n < 1) return false; while (n % 3 == 0){ n /= 3; } return n == 1; } } ``` ## Java Solution ```java class Solution { public boolean isPowerOfThree(int n) { return n > 0 && 1162261467 % n == 0; } } ``` ## Python Solution ```python class Solution: def isPowerOfThree(self, n): """ :type n: int :rtype: bool """ return n > 0 and 1162261467 % n == 0 ```

13.869565

106

0.502612

eng_Latn

0.315767

e9459be466535807728046779883e29144a86474

690

md

Markdown

flow-typed/README.md

gawkermedia/traverse-dom

e2452cd969510bcccfa2195919b2dd31045a251f

[ "MIT" ]

4

2016-11-02T10:29:10.000Z

2021-02-05T14:33:14.000Z

flow-typed/README.md

gawkermedia/traverse-dom

e2452cd969510bcccfa2195919b2dd31045a251f

[ "MIT" ]

5

2016-11-03T09:56:11.000Z

2022-02-12T11:21:19.000Z

flow-typed/README.md

gawkermedia/traverse-dom

e2452cd969510bcccfa2195919b2dd31045a251f

[ "MIT" ]

1

2021-02-24T17:21:58.000Z

## flow-typed The definitions under the `npm` folder here are pulled down from [`flow-typed`](https://github.com/flowtype/flow-typed). Please do not change these files directly. ### Updating these definitions 1. Put up a pull request on [`flow-typed`](https://github.com/flowtype/flow-typed) with the proposed changes. Include tests. 2. Once it's merged, update the files here - `npm install -g flow-typed` - `flow-typed install packageName -f flowVersion -o`, where: - `packageName` is the name of the package (e.g. `mocha@2.4.0`) - `flowVersion` is the Flow version we are currently using e.g. `0.33.0` - `-o` just indicates the the existing defs should be overwritten

46

124

0.718841

eng_Latn

0.993978

e946f7a652a180adce8540877b83e9c73c38e6ac

1,574

md

Markdown

desktop-src/DirectShow/csystemclock.md

citelao/win32

bf61803ccb0071d99eee158c7416b9270a83b3e4

[ "CC-BY-4.0", "MIT" ]

4

2021-07-26T16:18:49.000Z

2022-02-19T02:00:21.000Z

desktop-src/DirectShow/csystemclock.md

citelao/win32

bf61803ccb0071d99eee158c7416b9270a83b3e4

[ "CC-BY-4.0", "MIT" ]

2

2020-04-09T17:00:51.000Z

2020-04-09T18:30:01.000Z

desktop-src/DirectShow/csystemclock.md

citelao/win32

bf61803ccb0071d99eee158c7416b9270a83b3e4

[ "CC-BY-4.0", "MIT" ]

2

2020-07-19T02:58:48.000Z

2021-03-06T21:09:47.000Z

--- Description: The CSystemClock class implements a clock that returns the system time. ms.assetid: 22f8b641-6472-433f-bff4-4e62eae25c9b title: CSystemClock class ms.topic: reference ms.date: 05/31/2018 topic_type: - APIRef - kbSyntax api_name: - CSystemClock api_type: - COM api_location: --- # CSystemClock class ![csystemclock class hierarchy](images/sclock01.png) The `CSystemClock` class implements a clock that returns the system time. This class derives from the [**CBaseReferenceClock**](cbasereferenceclock.md) class, and adds support for the **IPersist** and [**IAMClockAdjust**](/windows/desktop/api/Strmif/nn-strmif-iamclockadjust) interfaces. | Public Methods | Description | |-------------------------------------------------------|-----------------------------------------------------| | [**CreateInstance**](csystemclock-createinstance.md) | Creates a new instance of this object. | | [**CSystemClock**](csystemclock-csystemclock.md) | Constructor method. | | IAMClockAdjust Methods | Description | | [**SetClockDelta**](csystemclock-setclockdelta.md) | Adjusts the clock time. | | IPersist Methods | Description | | [**GetClassID**](csystemclock-getclassid.md) | Returns the class identifier (CLSID) of the object. |

34.217391

213

0.548285

eng_Latn

0.520343

e9488cd595ec081a7cec49ab042ee45d3568d63c

119

md

Markdown

slides/talk2/089_plot.md

CSC510-2015-Axitron/txts

cc3403b7d6efa6143670dc8134521bcb8bdfe34f

[ "MIT" ]

null

slides/talk2/089_plot.md

CSC510-2015-Axitron/txts

cc3403b7d6efa6143670dc8134521bcb8bdfe34f

[ "MIT" ]

null

slides/talk2/089_plot.md

CSC510-2015-Axitron/txts

cc3403b7d6efa6143670dc8134521bcb8bdfe34f

[ "MIT" ]

null

# Plot and Function Function displayed below: $f(x,y)=sin(x^2+y^2)$ <img align=center src="../img/plot/plot1.png">

13.222222

46

0.663866

eng_Latn

0.517633

e9488d6c809a741ea39d92afa0da06b63d29842c

241

md

Markdown

Methods/speechSupported.md

sawyerbutton/Artyom.js-Translation

3f9c46bd368e1873c1aa7879ce7993af56efc37b

[ "MIT" ]

null

Methods/speechSupported.md

sawyerbutton/Artyom.js-Translation

3f9c46bd368e1873c1aa7879ce7993af56efc37b

[ "MIT" ]

null

Methods/speechSupported.md

sawyerbutton/Artyom.js-Translation

3f9c46bd368e1873c1aa7879ce7993af56efc37b

[ "MIT" ]

null

# speechSupported 验证 speechSynthesis 是否被当前浏览器支持。 SpeechSynthesis接口是用于控制文本到语音输出的脚本化Web API。该函数允许你检查 Speech Synthesis API 是否在当前浏览器中使用。 ```javascript if(artyom.speechSupported()){ // Use artyom.say("Text"); }else{ // Unsupported :/ } ```

18.538462

83

0.755187

yue_Hant

0.487785

e9490801acba52f6f4e6c3f30f3b01745d1d6265

6,306

md

Markdown

_posts/2011-12-05-iud-2.md

bazhuamed/bazhuamed.github.io

abb7dc6d3959c65f0b904c68026a94cc19aae60b

[ "MIT" ]

null

_posts/2011-12-05-iud-2.md

bazhuamed/bazhuamed.github.io

abb7dc6d3959c65f0b904c68026a94cc19aae60b

[ "MIT" ]

null

_posts/2011-12-05-iud-2.md

bazhuamed/bazhuamed.github.io

abb7dc6d3959c65f0b904c68026a94cc19aae60b

[ "MIT" ]

null

--- id: 7891 title: 直面节育环的困惑 date: 2011-12-05T07:00:36+00:00 author: Juneo excerpt: 最近，一条关于节育环的微博引起不小震动。“不断动作的节育环刮擦子宫壁”、“造成流产”，“本质是一种长期的刮宫流产术”的描述让人看后胆战心惊。节育器的作用方式果真如此吗？它的安全性如何？是时候来了解一下了！ layout: post guid: http://www.bazhua.org/?p=7891 permalink: /iud-2/ sfw_comment_form_password: - q5rjXzrxAoF9 cb_bg_image_post_setting: - "1" cb_review_checkbox: - "0" cb_score_display_type: - percentage cb_placement: - top cb_user_score: - 'on' cb_featured_post_menu: - 'off' cb_featured_post: - 'off' cb_featured_cat_post: - 'off' cb_featured_image_style: - standard cb_full_width_post: - sidebar image: /wp-content/uploads/2011/12/exjfl8-125x125.jpg categories: - 两性 - 妇产科学 tags: - 女性 - 避孕 --- <p style="padding-left: 30px"> <strong>最近，一条关于节育环的微博引起不小震动。“不断动作的节育环刮擦子宫壁”、“造成流产”，“本质是一种长期的刮宫流产术”的描述让人看后胆战心惊。节育器的作用方式果真如此吗？它的安全性如何？是时候来了解一下了！</strong> </p> [<img class="alignleft size-full wp-image-7898" src="/wp-content/uploads/2011/12/exjfl8.jpg" alt="" width="260" height="196" srcset="/wp-content/uploads/2011/12/exjfl8.jpg 260w, /wp-content/uploads/2011/12/exjfl8-150x113.jpg 150w, /wp-content/uploads/2011/12/exjfl8-80x60.jpg 80w" sizes="(max-width: 260px) 100vw, 260px" />](/wp-content/uploads/2011/12/exjfl8.jpg)**流言：** 去你妈的节育环。环的原理是：不断动作的节育环刮擦子宫壁，造成子宫无菌性炎症，使胚胎无法在子宫内正常着床受孕，从而造成流产，以达到避孕的目的，其本质是一种长期的刮宫流产术。 **真相：** 节育环就是宫内节育器，尽管其形状已经从最初的环形发展到各式各样的形状，老百姓依然保留了“环”这一俗称。在中国，据统计有40%的妇女使用宫内节育器避孕，约占全世界的60%<sup>[1]</sup>。面对如此高的使用率，这样的一则流言无疑让人看后胆战心惊，尤其是流言中用到 “刮擦”、“流产”、“刮宫流产术”这样的词汇。节育器到底通过什么样的方式达到避孕目的的呢？它的安全性如何呢？要回答这些问题，先得了解下节育器的种类。 ### 节育器的种类国内外目前存在的节育器形态各异，依据作用机理主要可分为两大类，一类叫惰性宫内节育器，另一类叫活性宫内节育器。惰性宫内节育器顾名思义就是用惰性材料如不锈钢、金、银、塑料、尼龙、硅橡胶等材料制成，国外主要为Lippes蛇形和Dulkon盾形节育器，国内主要为不锈钢圆环，这也是“环”的由来。不过，随着新一代的宫内节育器——活性宫内节育器的全面推广，这类的节育器已于1993年停止生产。活性宫内节育器是在既往惰性材料作为支架的基础上，在支架表面涂以活性物质如铜离子、激素、药物及磁性物质等，提高避孕效果，减少副反应。目前国内主要应用的是带铜节育器（宫形、T形、V形）和含孕激素的宫内节育器<sup>[2]</sup>。 [<img class="alignnone size-full wp-image-7900" src="/wp-content/uploads/2011/12/vbvi6c.jpg" alt="" width="389" height="279" srcset="/wp-content/uploads/2011/12/vbvi6c.jpg 389w, /wp-content/uploads/2011/12/vbvi6c-150x107.jpg 150w, /wp-content/uploads/2011/12/vbvi6c-300x215.jpg 300w" sizes="(max-width: 389px) 100vw, 389px" />](/wp-content/uploads/2011/12/vbvi6c.jpg) _各式各样的宫内节育器_ ### 节育器的避孕机制不同类型的节育器作用方式稍有不同，但总的来说，是通过多个环节上的作用，干扰精子生存、运行和受精，干扰受精卵的运行及着床来实现避孕的。惰性节育器材料本身作为异物压迫刺激子宫内膜，一方面引起一种无菌性的炎症反应，增加了宫腔内白细胞、淋巴细胞、巨噬细胞等炎性细胞的数目及其分泌的物质，使子宫液的成分发生改变，可以影响精子在宫腔及输卵管内的活动度，干扰胚泡的运输速度和杀灭胚泡；另一方面可以使子宫内膜产生较多前列腺素，前列腺素可以改变输卵管蠕动，使受精卵的运行和子宫内膜发育不同步，从而影响受精卵着床<sup>[3]</sup>。带铜节育器是在惰性节育器作用机制的基础上，增加了铜离子的长期缓慢释放，增高的铜离子浓度一方面干扰了子宫内膜细胞的代谢，使得受精卵种植的“土壤”变得贫瘠，无法着床种植。另一方面，对精子也有毒性作用，辅助增强避孕效果<sup>[3]</sup>。研究表明，这些局部微量释放的铜离子被子宫内膜吸收后只是使宫腔液内铜离子浓度局部增高，并不改变血清中的铜离子浓度，因此不对人体其他部位产生危害<sup>[4,5]</sup>，但对铜离子过敏的女性不适宜使用带铜节育器。同样，含孕激素的节育器也是在惰性节育器作用机制的基础上，增加了孕酮或者其替代品炔诺孕酮的缓慢释放。局部孕激素浓度增高后，一方面可以抑制子宫内膜生长，内膜腺体和间质细胞生长受限，干扰受精卵着床；另一方面，能促使宫腔内酶发生变化，使宫颈粘液变稠，增大精子运行的难度<sup>[3]</sup>。孕激素带来的副作用是早期避孕药倍受诟病的原因，但因为节育器能做到局部微量直接给药，不会反馈抑制垂体—卵巢轴的功能<sup>[6]</sup>，避免了可能的副作用。 [<img class="alignnone size-full wp-image-7899" src="/wp-content/uploads/2011/12/8jkkyp.jpg" alt="" width="513" height="263" srcset="/wp-content/uploads/2011/12/8jkkyp.jpg 513w, /wp-content/uploads/2011/12/8jkkyp-150x76.jpg 150w, /wp-content/uploads/2011/12/8jkkyp-300x153.jpg 300w" sizes="(max-width: 513px) 100vw, 513px" />](/wp-content/uploads/2011/12/8jkkyp.jpg) _含孕激素的宫内节育器，作用示意图（左）和实物（右）_ 除了避孕的作用外，目前处于研发和临床试验阶段的新一代宫内节育器将在支架表面加用药物，希望能用来治疗痛经、月经紊乱或经血过多等妇科疾病。 ### 节育环 ≠ 刮宫流产术流言将节育器的本质比喻为“刮宫流产术”是不正确的，夸大了节育器的机械物理作用，而忽略了节育器更主要的生物化学作用。无论是惰性节育器还是活性节育器，都没有通过流言中所说的物理手段“刮”或者“擦”来直接破坏子宫内膜，而是通过前列腺素、铜离子或者微量的孕酮来间接干扰子宫内膜细胞的代谢，阻碍子宫内膜与试图着床的受精卵同步发展，导致受精卵没有适宜的内膜来种植，最终排出了体外。而子宫内膜则仍然按照个人的月经周期发展，等到经期开始，在人体自身分泌的激素作用下，正常脱落，排出体外。节育器的压迫刺激造成的无菌性炎症是人体面对无菌性异物刺激时局部免疫力增强的正常现象。当宫腔内有活动的精子和受精卵时，这种局部增强的免疫力可以起到杀灭精子和受精卵的作用。这个炎症反应的强度跟我们平时身体局部挫伤后的红肿类似，对人体自身没有害处。在美国妇产科协会（ACOG）2005年的指南里，明确指出宫内节育器可以提供安全、有效、可逆、长期的避孕效果，建议女性使用。2007年，美国妇产科协会召开题为“宫内节育器与青少年”的会议后，由美国疾病预防控制机构CDC和世界卫生组织WHO共同建议扩大宫内节育器的使用人群，其中也包括18岁以下有性生活的女性和未产女性<sup>[7]</sup>。一些人对节育环是否会诱发子宫内膜癌存在顾虑，但是根据国外的流行病学研究，甚至观察到宫内节育器有降低子宫内膜癌发病的作用，尽管具体的机制尚未阐明，但希望这个证据可以消除广大女性的不安<sup>[8]</sup>。 ### 节育器的副作用任何一种医疗措施都不可避免有出现副作用的可能，节育器也不例外。常见的副作用有以下几个方面： **感染：** 放置或取出节育器后2~ 3 天可能会出现下腹隐痛并逐渐加剧，伴随体温升高时要考虑到有感染的可能，建议大家及时去医院就诊。感染多数是由于操作不当或放置后未注意卫生引起的，建议接受节育器放置或取出术的女性要注意休息，注意会阴区卫生。 **月经异常：** 支撑力较高或子宫内膜接触面积较广的节育器容易损伤内膜导致出血，表现为经期出血过多、经期延长，一般3个月之内可以缓解，同时建议定期去医院复查，出血时间延长可加用抗生素预防感染。 **疼痛：** 在放置后10天以内，因异物刺激子宫收缩，可能会出现类似痛经的症状，一般1个月左右会逐渐缓解，必要时可以服用止痛药对症治疗。 **白带增多：** 由于宫腔液体及宫颈粘液的变化，可能增加白带的分泌。排除感染的可能后，一般情况下无需治疗，会自行减少。 **子宫穿孔：** 随着目前节育器形状和质量的改善，子宫穿孔的并发症比较罕见，一般都是由于操作人员技术问题所致，建议想“上环”的女性务必前往正规医院<sup>[9]</sup>。 **带器妊娠：** 这意味着节育环避孕失败。国内外资料显示，带器妊娠的发生率为1%-3%，避孕失败与节育器所选类型、节育器移位、带铜节育器铜离子浓度等相关，目前公认的失败率较低的节育器有TCu380 和 (LNG) IUD<sup>[10]</sup>。此外，放置节育器也是有禁忌症的。如果已经怀孕（包括疑似），或者三个月内有感染性流产，患有急性盆腔炎，感染性子宫内膜炎，未治疗的宫颈炎，恶性肿瘤（包括疑似），存在出血问题，或者是已经有环的人，是不能接受上环的<sup>[2]</sup>。 **结论：** 除却强制上环的无奈，节育器作为全世界都在使用和推行的避孕方法，在避孕机制上是安全可靠的，并不像流言中描述的那般可怕。使用节育环避孕也有它独特的优点，比如不必天天服药，对药物不耐受（胃肠刺激等）的人是个很好的补充，也不影响女性内分泌和正常月经，取出节育器之后可以恢复正常的生育能力。但是与避孕套相比，节育器并不能够预防性病。女性在选择避孕方式时，有必要正确了解各种避孕方法的特点和适用范围，结合自身的情况合理使用才是正确的态度。 **注意：节育器的作用只是避孕，不能预防性传播疾病。该带套的时候可不能省哦！** > 参考文献： > [1] Xiao Bilian,Chinese experience with intrauterine devices, Contraception 75 (2007) S31–34 > [2] 《妇产科学（八年制第2版）》，丰有吉，人民卫生出版社 > [3] Joseph B. Stanford, MD, Mechanisms of action of intrauterine devices: Update and estimation of postfertilization effects, Volume 187, Number 6 Am J Obstet Gynecol ,1699-1708 > [4] 杜天竹, 置CuIUD妇女血清及宫腔冲洗液Cu~(2+)浓度的近期测定[J]. 微量元素与健康研究, 2004,(05) > [5] 王昕; 顾向应,带器妊娠妇女血清，组织铜的相关研究,天津医科大学优秀硕士论文集 > [6] 张美云,缓慢释放孕酮宫内节育器的体内释药研究及对垂体—卵巢轴影响的探讨[J]. 生殖与避孕, 1986,(03) . > [7] David Hubacher,Renewed interest in intrauterine contraception in the United States:Evidence and explanation Contraception 83 (2011) 291–294. > [8] SUSAN R STURGEON,*Intrauterine Device Use and Endometrial Cancer Risk, International Journal of Epidemiology,Vol. 26, No. 3. > [9] Kimberley, A Clinical Review of the Intrauterine Device as an Effective Method of Contraception, JOGNN, 38, 693-698; 2009. > [10] Patrick ThonneauRisk factors for intrauterine device failure: a review, Contraception,Volume 64, Issue 1, July 2001, Pages 33-37. <pre>已发布于果壳<a href="http://www.guokr.com/article/75859/" target="_blank">谣言粉碎机</a></pre>

47.413534

457

0.796067

yue_Hant

0.556128

e9499e396e7e2862b669f71bc37a14bb5b13e7a7

1,923

md

Markdown

map/providers/bingmaps/tiles.md

attilaantal/winforms-docs

c311033085e6f770435eaa3c921edde9efcb12dd

[ "MIT" ]

30

2016-02-18T13:23:42.000Z

2021-09-23T01:26:05.000Z

map/providers/bingmaps/tiles.md

attilaantal/winforms-docs

c311033085e6f770435eaa3c921edde9efcb12dd

[ "MIT" ]

25

2016-03-16T07:13:47.000Z

2021-07-30T13:31:24.000Z

map/providers/bingmaps/tiles.md

attilaantal/winforms-docs

c311033085e6f770435eaa3c921edde9efcb12dd

[ "MIT" ]

183

2016-02-19T09:56:35.000Z

2022-01-17T18:03:36.000Z

--- title: Tiles page_title: Tiles | RadMap description: RadMap can visualize tile data from the Bing Maps and the OpenStreetMaps REST services as well as from the local file system. slug: winforms/map/providers/tiles tags: map, providers published: True position: 1 --- # Tiles [Bing Maps](https://www.bingmapsportal.com/) provide a world map that users can easily pan and zoom. In order to achieve smooth users interaction, the map is pre-rendered at many detailed levels where each level is cut into tiles of 256 x 256 pixels each. Each tile is given XY coordinates ranging from (0, 0) in the upper left to (2<sup>level</sup>–1, 2<sup>level</sup>–1) in the lower right. For example, at level 3 the tile coordinates range from (0, 0) to (7, 7) as follows: >caption Figure 1: Tile XY coordinates at level 3 ![map-tiles 001](images/map-tiles001.png) In order to optimize the tiles indexing, the two-dimensional tile XY coordinates are combined into one-dimensional strings called quadtree keys, or “quadkeys” for short. Each quadkey uniquely identifies a tile and it can be used as a key in common database B-tree indexes. To convert tile coordinates into a quadkey, the bits of the Y and X coordinates are interleaved, and the result is interpreted as a base-4 number (with leading zeros maintained) and converted into a string. For instance, given tile XY coordinates of (3, 5) at level 3, the quadkey is determined as follows: tileX = 3 = 011<sub>2</sub> tileY = 5 = 101<sub>2</sub> quadkey = 100111<sub>2</sub> = 213<sub>4</sub> = “213” >caption Figure 2: Tile Quadkeys ![map-tiles 002](images/map-tiles002.png) Finally, tiles that are close to each other have quadkeys that are relatively close together. This is important for optimizing performance, because neighboring tiles are usually requested in groups. # See Also * [Bing Maps Tile System](https://msdn.microsoft.com/en-us/library/bb259689.aspx)

54.942857

579

0.76235

eng_Latn

0.996241

e94b0576d631bb828fcd6149727d0e0fcded23f0

107

md

Markdown

ringlibs/naturallib/README.md

benkarime/ring

c2ef3687918e8c21b9c314a6c4f7a3a9a1688751

[ "MIT" ]

1,086

2016-03-24T23:22:11.000Z

2022-03-28T22:35:03.000Z

libraries/naturallib/README.md

zaka7024/ring

97cb48f44be3f5522a85610f70d7ec904d19fe57

[ "MIT" ]

1,095

2016-04-10T18:15:33.000Z

2022-03-31T18:21:20.000Z

libraries/naturallib/README.md

zaka7024/ring

97cb48f44be3f5522a85610f70d7ec904d19fe57

[ "MIT" ]

516

2016-03-29T19:41:27.000Z

2022-03-07T20:10:56.000Z

NaturalLib ========== Create domain-specific programming languages that uses natural language programming!

26.75

84

0.785047

eng_Latn

0.958901

e94ba00619627525e6fc1730ea8d72942d87dfd2

5,637

md

Markdown

README.md

Chen-Jialin/Contents-Undergraduate

08a2431e6bc0c08abccc8c9f5443a98d9ef802a6

[ "MIT" ]

1

2022-03-07T08:22:17.000Z

README.md

Chen-Jialin/Contents-Undergraduate

08a2431e6bc0c08abccc8c9f5443a98d9ef802a6

[ "MIT" ]

null

README.md

Chen-Jialin/Contents-Undergraduate

08a2431e6bc0c08abccc8c9f5443a98d9ef802a6

[ "MIT" ]

1

2022-03-22T08:43:09.000Z

# Contents-Undergraduate 本科期间（2017下半年 - 2021上半年）工作汇总。 [English version](README_en.md) ## 大一上：2017-2018 学年第一学期 - 普通物理 IA（PHYS1101） - [作业](https://github.com/Chen-Jialin/General-Physics-IA-Assignments) - [小抄](https://github.com/Chen-Jialin/General-Physics-IA-CheatSheet) - 普通化学 IB（CHEM1102） - [作业](https://github.com/Chen-Jialin/General-Chemistry-IB-Assignments) - 综合英语（GEHA1039） - [作业](https://github.com/Chen-Jialin/General-English-II-Assignments) ## 大一下：2017-2018 学年第二学期 - 普通物理 IIA（PHYS1103） - [作业](https://github.com/Chen-Jialin/General-Physics-IIA-Assignments) - [课程项目：自制收音机](https://github.com/Chen-Jialin/General-Physics-IIA-Project-Homemade-Radio) - [考试](https://github.com/Chen-Jialin/General-Physics-IIA-Exams) - 普通物理 II 实验（PHYS1113） - [实验报告](https://github.com/Chen-Jialin/General-Physics-II-Lab-Reports) - 信息科学技术导论（SI100B） - [作业和课程论文](https://github.com/Chen-Jialin/SI100B-Introduction-to-Infomation-Science-and-Technology-Assignments) - 综合英语 III（GEHA1040） - [作业](https://github.com/Chen-Jialin/General-English-III-Assignments) ## 大二上：2018-2019 学年第一学期 - 光学（PHYS1381） - [作业](https://github.com/Chen-Jialin/Optics-Assignments) - [小抄](https://github.com/Chen-Jialin/Optics-CheatSheets) - [期中考试](https://github.com/Chen-Jialin/Optics-Midterm-Exam) - 理论力学（PHYS1302） - [作业](https://github.com/Chen-Jialin/Theoretical-Mechanics-Assignments) - [考试](https://github.com/Chen-Jialin/Theoretical-Mechanics-Exams) - 光学实验（PHYS1311） - [实验报告](https://github.com/Chen-Jialin/Optical-Lab-Reports) ## 大二下：2018-2019 学年第二学期 - 电动力学（PHYS1304） - [作业](https://github.com/Chen-Jialin/Electrodynamics-Assignments) - [小抄](https://github.com/Chen-Jialin/Electrodynamics-CheatSheets) - 普通化学 II（CHEM1111） - [作业](https://github.com/Chen-Jialin/General-Chemistry-II-Assignments) - 数学物理方法 II（PHYS1303） - [作业](https://github.com/Chen-Jialin/Mathematical-Methods-for-Physics-II-Assignments) - [小抄](https://github.com/Chen-Jialin/Mathematical-Methods-for-Physics-II-CheatSheet) - 概率论与数理统计（SI140） - [作业](https://github.com/Chen-Jialin/Probability-and-Statistics-Assignments) - 数值分析（GEMA1008） - [上机实验报告](https://github.com/Chen-Jialin/Numerical-Analysis-Hands-on-Experiments) ## 大三上：2019-2020 学年第一学期 - 统计物理（PHYS1503） - [作业](https://github.com/Chen-Jialin/Statistical-Mechanics-Assignments) - [小抄](https://github.com/Chen-Jialin/Statistical-Mechanics-CheatSheets) - [期中考试](https://github.com/Chen-Jialin/Statistical-Mechanics-Midterm-Exam) - 量子力学（PHYS1501） - [作业](https://github.com/Chen-Jialin/Quantum-Mechanics-Assignments) - [期中考试](https://github.com/Chen-Jialin/Quantum-Mechanics-Midterm-Exam) - 晶体衍射学（PHYS1551） - [作业](https://github.com/Chen-Jialin/Diffraction-Crystallography-Assignments) - 激光原理技术（PHYS1553） - [作业](https://github.com/Chen-Jialin/Laser-Principles-and-Technologies-Assignments) - 随机模拟方法与应用导论（MATH1114） - [作业](https://github.com/Chen-Jialin/Intro-to-Stochastic-Simulation-Methods-and-its-Application-Assignments) ## 大三下：2019-2020 学年第二学期 - 固体物理（PHYS1502） - [作业](https://github.com/Chen-Jialin/Solid-State-Physics-Assignments) - [小抄](https://github.com/Chen-Jialin/Solid-State-Physics-CheatSheet) - 非线性光学（PHYS2202） - [作业](https://github.com/Chen-Jialin/Nonlinear-Optics-Assignments) - 计算物理（PHYS1504） - [练习、作业和课程项目](https://github.com/Chen-Jialin/Computational-Physics-Exercises-and-Assignments) - 近代物理实验（PHYS1701） - [实验报告](https://github.com/Chen-Jialin/Modern-Physics-Lab-Reports) - 原子物理中的量子力学实验（PHYS1704） - [课程论文](https://github.com/Chen-Jialin/Quantum-Physics-Lab-in-Atomic-Physics-Essay) - 群论（PHYS2102） - [作业](https://github.com/Chen-Jialin/Group-Theory-Assignments) ## 大四上：2020-2021 学年第一学期 - 研究型物理实验（PHYS1703） - [实验笔记](https://github.com/Chen-Jialin/Explorative-Physics-Laboratory-Notes) - [实验报告](https://github.com/Chen-Jialin/Explorative-Physics-Laboratory-Reports) - 通信原理（EE140） - [作业](https://github.com/Chen-Jialin/Communication-System-Assignments) - [小抄](https://github.com/Chen-Jialin/CommunicationSystemCheatSheet) - [期中考试](https://github.com/Chen-Jialin/Communication-System-Midterm-Exam) - 导波光学（EE290C） - [作业](https://github.com/Chen-Jialin/Guided-Wave-Optics-Assignments) - [小抄](https://github.com/Chen-Jialin/Guided-Wave-Optics-CheatSheets) - [课程项目](https://github.com/Chen-Jialin/Guided-Wave-Optics-Project) - 在生活中感知材料的魅力（GENS1004） - [作业](https://github.com/Chen-Jialin/Inspiration-of-Materials-from-Life-and-Nature-Assignments) - 天文学基础与飞行器设计（GENS1006） - [课堂实践](https://github.com/Chen-Jialin/Astronomy-Basics-and-Spacecraft-Design-Practice) ## 大四下：2020-2021 学年第二学期 - 高等热力学与统计物理（PHYS2110） - [作业](https://github.com/Chen-Jialin/Advanced-Thermodynamics-and-Statistical-Physics-Assignments) - [期末考试](https://github.com/Chen-Jialin/Advanced-Thermodynamics-and-Statistical-Physics-Final-Exam) - 毕业论文（PHYS1990） - [硒化镉量子点的二维光谱探测](https://github.com/Chen-Jialin/Undergraduate-Thesis) ## 其他 - [2019 年数学建模美赛](https://github.com/Chen-Jialin/ICM-2019) - 2019 全国大学生物理学术竞赛（CUPT） - [第 1 题：电晕放电驱动马达](https://github.com/Chen-Jialin/CUPT-2019-Problem-1-Invent-Yourself) - [第 6 题：飓风球](https://github.com/Chen-Jialin/CUPT-2019-Problem-6-Hurricane-Balls) - [第 9 题：酱油光学](https://github.com/Chen-Jialin/CUPT-2019-Problem-9-Soy-Sauce-Optics) - [第 13 题：莫尔织物计数器](https://github.com/Chen-Jialin/CUPT-2019-Problem-13-Moire-Thread-Counter) - [第 14 题：循环摆](https://github.com/Chen-Jialin/CUPT-2019-Problem-14-Looping-Pendulum) - [2019 高教杯全国大学生数学建模竞赛](https://github.com/Chen-Jialin/CUMCM-2019) - [教师资格证考试主观题记忆内容归纳](https://github.com/Chen-Jialin/Teacher-Certification-Exam-Summary) - [2020 年数学建模美赛](https://github.com/Chen-Jialin/ICM-2020)

48.179487

114

0.745609

yue_Hant

0.972745

e94bad45a5451228ed60ad7e412efa7a1e6e9c87

577

md

Markdown

_posts/2018-11-10-JVM-01-CodeExecution.md

seventheluck/seventheluck.github.io

0585ff9db2006b33351ba43be15b37d4c293f740

[ "MIT" ]

null

_posts/2018-11-10-JVM-01-CodeExecution.md

seventheluck/seventheluck.github.io

0585ff9db2006b33351ba43be15b37d4c293f740

[ "MIT" ]

null

_posts/2018-11-10-JVM-01-CodeExecution.md

seventheluck/seventheluck.github.io

0585ff9db2006b33351ba43be15b37d4c293f740

[ "MIT" ]

null

--- layout: post title: JVM 01 Code execution categories: Java description: JVM 01 Code execution keywords: Java, JVM --- #### Interpres and Execution compilation Interpres and execution means translate bytecode to machine code one by one. Advantage: don't need to wait for copilation. #### Just-In-Time compilation(JIT) Execution after compilation the whole method. Advantage: run faster than above. Hotspot use the combination of these two methods by default. It interprets the bytecode first. If part of the bytecode executed repeatedly, it will use JIT each method unit.

33.941176

173

0.786828

eng_Latn

0.994403

e94caaf9ddad5c66a3dacda5b0c2a0aec3c8e7d7

1,781

md

Markdown

source/install/_install-mac.md

nanobox-io/nanobox-docs

8e8d2d9346fb26f4e44da5c51dd2e7896a4f11a4

[ "MIT" ]

12

2015-11-19T19:44:16.000Z

2021-11-08T10:27:35.000Z

source/install/_install-mac.md

nanobox-io/nanobox-docs

8e8d2d9346fb26f4e44da5c51dd2e7896a4f11a4

[ "MIT" ]

54

2015-11-25T16:31:58.000Z

2019-01-06T23:02:28.000Z

source/install/_install-mac.md

nanobox-io/nanobox-docs

8e8d2d9346fb26f4e44da5c51dd2e7896a4f11a4

[ "MIT" ]

21

2016-01-16T05:58:24.000Z

2021-09-13T04:06:39.000Z

**Note:** _There are known issues with installing and running Nanobox on MacOS 10.13 - High Sierra. For detailed instructions, view the [Installing Nanobox on MacOS High Sierra](https://content.nanobox.io/installing-nanobox-on-macos-high-sierra/) article._ ## System Requirements System requirements depend on how you're going to run Nanobox. You can either use a lightweight VM (VirtualBox) or Native Docker. _**For MacOS, we recommend using the lightweight VM option. Docker's MacOS filesystem driver is slow.**_ ### Lightweight VM (VirtualBox) - MacOS 10.10+ - VirtualBox - _A version of the [Nanobox installer](#download-amp-run-nanobox-installer) includes VirtualBox._ #### netfs Requirements During the intitial setup process, you'll specify how code is mounted into VM. "netfs" is the more performant option. - `nfsd` enabled and running ### Native Docker - MacOS 10.11+ - [Docker for Mac](https://docs.docker.com/docker-for-mac/) ## Download & Run the Nanobox Installer Download the Nanobox installer from the [Nanobox downloads page](https://dashboard.nanobox.io/download). Run it and it will walk you through the entire installation process. _**Note:** If you plan on going with the lightweight VM option and already have VirtualBox installed, you can select the "Use Docker Native" option. This will download an installer that only includes the Nanobox binary._ ## Run & Setup Nanobox The first time you run any [Nanobox command](/cli/), it will walk you through an initial setup process to configure things like RAM, CPU, and other things related to your local environment. ## Start Hacking! With Nanobox installed, the [Getting Started Guides](https://guides.nanobox.io) walk you through getting popular languages and frameworks up and running with Nanobox.

57.451613

256

0.775407

eng_Latn

0.989696

e94ed9ff19b4e08611918fe1d3dc7877972c474d

537

md

Markdown

about.md

gmarnin/nstrauss.github.io

b329155b795329aa077f090c9027d5aa4954e96b

[ "MIT" ]

null

about.md

gmarnin/nstrauss.github.io

b329155b795329aa077f090c9027d5aa4954e96b

[ "MIT" ]

null

about.md

gmarnin/nstrauss.github.io

b329155b795329aa077f090c9027d5aa4954e96b

[ "MIT" ]

2

2020-08-16T19:41:18.000Z

2020-08-16T19:53:47.000Z

--- layout: page title: About permalink: /about/ --- I'm an IT manager doing Apple related things at a K-12 public school district. 1:1 program, Mac, iPad, Apple TV, and systems engineering. Probably going to write mostly about Apple device management. I hope sometimes the things I write are useful to you. # Social Media - [GitHub](https://github.com/nstrauss) - [Twitter](https://twitter.com/nwstrauss_) - [LinkedIn](https://linkedin.com/in/nathaniel-strauss) @nstrauss on [MacAdmins](https://www.macadmins.org/) Slack team.

28.263158

82

0.73743

eng_Latn

0.912913

e94eddbec7a506d312177d0390653612a5734e01

218

md

Markdown

_watches/M20210630_091225_TLP_1.md

Meteoros-Floripa/meteoros.floripa.br

7d296fb8d630a4e5fec9ab1a3fb6050420fc0dad

[ "MIT" ]

5

2020-05-19T17:04:49.000Z

2021-03-30T03:09:14.000Z

_watches/M20210630_091225_TLP_1.md

Meteoros-Floripa/site

764cf471d85a6b498873610e4f3b30efd1fd9fae

[ "MIT" ]

null

_watches/M20210630_091225_TLP_1.md

Meteoros-Floripa/site

764cf471d85a6b498873610e4f3b30efd1fd9fae

[ "MIT" ]

2

2020-05-19T17:06:27.000Z

2020-09-04T00:00:43.000Z

--- layout: watch title: TLP1 - 30/06/2021 - M20210630_091225_TLP_1T.jpg date: 2021-06-30 09:12:25 permalink: /2021/06/30/watch/M20210630_091225_TLP_1 capture: TLP1/2021/202106/20210629/M20210630_091225_TLP_1T.jpg ---

27.25

62

0.784404

eng_Latn

0.051742

e94edf84021b97e92cdece5f381a666958f80dfc

8,462

md

Markdown

_posts/2010-10-03-4862.md

TkTech/skins.tkte.ch

458838013820531bc47d899f920916ef8c37542d

[ "MIT" ]

1

2020-11-20T20:39:54.000Z

_posts/2010-10-03-4862.md

TkTech/skins.tkte.ch

458838013820531bc47d899f920916ef8c37542d

[ "MIT" ]

null

_posts/2010-10-03-4862.md

TkTech/skins.tkte.ch

458838013820531bc47d899f920916ef8c37542d

[ "MIT" ]

null

--- title: > Piggy layout: post permalink: /view/4862 votes: 1 preview: "data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAACUAAAAgCAIAAAAaMSbnAAAABnRSTlMA/wD/AP5AXyvrAAAD/klEQVRIie2Wu4/cVBSHz+Pe67Fnd7KP7G7I0gEF/xYIiRJqwkMUSFQUSBBRRKGhoII6EvwhSCiJEsGGPHZ3xo/7OOdQsfFI8Wgqqvyqn6XP/nx9ri2jmcJ/OfvmW5di0egqL4NYEnaYBG5+/glskec/3rUophmCY1BV7p8+qQ73jz748Iqh8QmIis5hMTHjEHDGIoXSsI0MACiV/uyxWen+fNB27fLsUR56yrbGjA9806hHPFgwBCFTMcgK3m3pk2KDCSpIznOrfLb5yU1qwqRPU2YKkAVrZkVU5eMFiMF2oYWviIEZ9+ZSs828DyG+6CZ9BgTBABHEJOWMCkPUnLf0wXkZ2gQMmgWWib2TVU8qkz5sUAYAwtxl9S74ULqBeFvdQP3+m0ewssXNG8nicLECFn+yM2bWZmPLqLOAgyKpJ2eVNw289fxcjwZaOPmWAs94gQaQuzTpY+/BsimicRw67NH5WrSD7cKuyCy4VgSzFvTzQIgwrI0Dn9y6Zaowp2f3H737w51XXuifTz+bYp5+/ZVEcPszSfLiwYPD09O//3h4eLqvL9pMVu3UEMlf371iyFCBVJ5GN70tNjLIHrBHNO+KlGGognCscEZBnFzk87/ujxkSwgIgta1inPJtYIY2C1MSYc9DjBZjXnZmK0MzAiI9fPutMUOwyq4rdNEvmtnkAqcZtx+YCL0NccCSDdlEYztwCkkyN4vh8bMxQ8UsKpj3Mv2ebWDcssgqqqqpWhG7TAyFG0htW8zK5fnlk8djhpgyc1GRDd+tTUxNysAFfE2H14+tu0jLaH2hRusaWG1xfDRmiNE5F1xdo6NXuQAANjByPkAx3g0lgnjvDhqsA7TJoU+XuYhSFcYMlT6Wtu+WnfLk+jYwvFf7vUraoWq8rC5TsYPTYzzZFXHzo2sKdnb/4ZhxAOi8B5SD64dTvg2MdALEOCO5iC5UYGTNHEWhMeyQ5+7k7XfGDAGiIM3rRlKZ1k0zbGCJPZJD98Y+ePae3c4OdMlIrM8uyZghIACGJEkZJ33TjHoDsDxYzEWWAyKk8ySXHcxCKYpEgjZmyBRVMFQhLJop3QamiIPgkXVWe7e7w35W3dhblYxQuRmBC2A4ZnD8//L8+9vQtzkLVZ6r+qofffTx5NJHeX73DgDDkMwzMlz1w/ffGz+pl5HYiTkygGLjvo0MAKQdLEZaBFIZ9zGztr/JkfQdUHCNM9WrvqXPL3YADLJoKuM+6SurPpkFn6QlleGqb+mDopIGAAOHa33KZ6uWFW0pcWGu7a76lrq4XFbXGslifYrxZR8za/f+xb17aPDl77/5Po37lj4mvP3Tz6Tuu19/Gfcxs7Y//4dsPZvXvtc+APgX2Xr9D9PjF6UAAAAASUVORK5CYII=" --- <dl class="side-by-side"> <dt>Preview</dt> <dd> <img class="preview" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAACUAAAAgCAIAAAAaMSbnAAAABnRSTlMA/wD/AP5AXyvrAAAD/klEQVRIie2Wu4/cVBSHz+Pe67Fnd7KP7G7I0gEF/xYIiRJqwkMUSFQUSBBRRKGhoII6EvwhSCiJEsGGPHZ3xo/7OOdQsfFI8Wgqqvyqn6XP/nx9ri2jmcJ/OfvmW5di0egqL4NYEnaYBG5+/glskec/3rUophmCY1BV7p8+qQ73jz748Iqh8QmIis5hMTHjEHDGIoXSsI0MACiV/uyxWen+fNB27fLsUR56yrbGjA9806hHPFgwBCFTMcgK3m3pk2KDCSpIznOrfLb5yU1qwqRPU2YKkAVrZkVU5eMFiMF2oYWviIEZ9+ZSs828DyG+6CZ9BgTBABHEJOWMCkPUnLf0wXkZ2gQMmgWWib2TVU8qkz5sUAYAwtxl9S74ULqBeFvdQP3+m0ewssXNG8nicLECFn+yM2bWZmPLqLOAgyKpJ2eVNw289fxcjwZaOPmWAs94gQaQuzTpY+/BsimicRw67NH5WrSD7cKuyCy4VgSzFvTzQIgwrI0Dn9y6Zaowp2f3H737w51XXuifTz+bYp5+/ZVEcPszSfLiwYPD09O//3h4eLqvL9pMVu3UEMlf371iyFCBVJ5GN70tNjLIHrBHNO+KlGGognCscEZBnFzk87/ujxkSwgIgta1inPJtYIY2C1MSYc9DjBZjXnZmK0MzAiI9fPutMUOwyq4rdNEvmtnkAqcZtx+YCL0NccCSDdlEYztwCkkyN4vh8bMxQ8UsKpj3Mv2ebWDcssgqqqqpWhG7TAyFG0htW8zK5fnlk8djhpgyc1GRDd+tTUxNysAFfE2H14+tu0jLaH2hRusaWG1xfDRmiNE5F1xdo6NXuQAANjByPkAx3g0lgnjvDhqsA7TJoU+XuYhSFcYMlT6Wtu+WnfLk+jYwvFf7vUraoWq8rC5TsYPTYzzZFXHzo2sKdnb/4ZhxAOi8B5SD64dTvg2MdALEOCO5iC5UYGTNHEWhMeyQ5+7k7XfGDAGiIM3rRlKZ1k0zbGCJPZJD98Y+ePae3c4OdMlIrM8uyZghIACGJEkZJ33TjHoDsDxYzEWWAyKk8ySXHcxCKYpEgjZmyBRVMFQhLJop3QamiIPgkXVWe7e7w35W3dhblYxQuRmBC2A4ZnD8//L8+9vQtzkLVZ6r+qofffTx5NJHeX73DgDDkMwzMlz1w/ffGz+pl5HYiTkygGLjvo0MAKQdLEZaBFIZ9zGztr/JkfQdUHCNM9WrvqXPL3YADLJoKuM+6SurPpkFn6QlleGqb+mDopIGAAOHa33KZ6uWFW0pcWGu7a76lrq4XFbXGslifYrxZR8za/f+xb17aPDl77/5Po37lj4mvP3Tz6Tuu19/Gfcxs7Y//4dsPZvXvtc+APgX2Xr9D9PjF6UAAAAASUVORK5CYII="> </dd> <dt>Original</dt> <dd> <img class="preview" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAEAAAAAgCAYAAACinX6EAAAABGdBTUEAALGPC/xhBQAAABh0RVh0U29mdHdhcmUAUGFpbnQuTkVUIHYzLjM2qefiJQAADmJJREFUaEPdmdlzW4d5xSEpnTz3j2n63KxNnGbaaTqJE9uyNlOiSIoU9xVcQHABSII7CUoURVIiKVl27bjJTCaZziR1+5LJJLXlWpREisRyVwCk36pOffr7rvtkPVCsXtRo5g4I4AK43/nOOd/5rk7EjvgXLC3rpE7EdOJpLPbfip049Wex2Cmex07GvvLVr/LSf/L8VOzEyVOxU5+fjD39/PPYV3j++dOnsZP6r9ifnz574qjfeKnfLy1lVVm+pnBuUeHsvMKFRZXWbii4dk2F+QmVV1ZVumHHDR1ubKrMUdnkuHVL4bVlvdTFPc/FhWvL8im8AhC5sVGFWcCg+HBhQblMSuH6TR1srql8a02l9VsUf1eV9XUdbm4oXLnxJwDA9Jz2B3ooek5PUoOqrK0oPzKicGlRhbEUzwFgY13Bxi0d3t1S5fZtur8RMaC8vPr/H4AgO6d8ekjhxrJyo4mIAbsDA6pA/f2xYZVWb6i0fFP+yooO79zR4RYyWF+Tv4ksYMrzsOylPqeM5p8M9SuYW9CTeDdS4Hl6RAfv3lVpYVmlLMf1FR2srqtyZ1OH77ytQ7p/sLGhA9jxUhf3PBdXvob2J0ciI3Qzo1D7ugqZNJ1fUbi4KH/5Bvqn8Hff1mf37qn8zh2V16A/R2n5T8AEy8vXlZsYZgrMqpJdwOBuKjeXoevLKtP1smk90vwmoMCC21+AUV5ZhxW3Xn4GuEMJBRO4++S4HjU2q5CIq5SZUDAzpWByCs3P68kw2kcK4UJWpZvoHd2Xr99QZQPD2wSAVSbAFrRfvanS0nWV374dTYXw5rpKK8swZUnB/JyC61k+t4CBLik3NCgff/kyC81Uw9lZeTPT8ofH5I5PKhwelZscUIjneIODcuNIEh8q9A7IT/Jeql/u0JCK8T65LXHlEjwftHN6j25AoadDu4lOPWxpVL6vS356QnvxTu11tmu3e0iFmRnl+NEKc97mf5jNom8c/917OvxH9P7OXTlLjMSZce2PjupJIkEmWAKIa5EEKpyf6++VPzfFd3YqNz3G78W1E++KCv0yAMHyksKZOfnT8/jOnLyJCZXS4/L6++WZGadS8gDP7Y3L6eiU39OjINmvfzp/Xh+cO6f3T5+WO9CnYCQhJzl4NAD7rZ3abmrgSwcoYEy/qG3ULxtaVJ6bURmNu1xECdpXtugy4668Bs3X6PzWhg5/dk8H793ltdv6MDGqf+2LR0XtDfYpn0wim2wUoB72dUeM2mnhe6dmlI/3yON7ywD1ZQBKeEoAQ1x+2wzXriGYnJA/k1GYHpNHFnEA2e3slhMHhLZWvf/GGxEbAqaU09XJaxyMbqet+2gAXGjzqLYGFJMqTWciABLf+qZ+3dUW/fjJ2AnZvzLdtMMKNwY8ffo0eu+A0GPFZ175nv65HQAWSYuLFE4IqtxEDuvL5IheJDCr3SSdWZqH/gMqMyId6P0MAyj6ALBd/Caw9DlNI6Zn5U+MqTQLCDDAhQ3BZIpie+QnevTe66/L6e3Wz86c4b1eOYMcHR0KUkNHA7Df3qsCHXPRjX35z2salPjOt/XrpiYFhCDroM380i9/pc9++6Eqv/kXHfB4+N49Bbcxus3b+m1PQpMA8Bu7oGk0S3fD2Rkuflblmay227iY7Kwe90FXii5C5SAzDaXHn/WAjTUd3Frle41pa9E1lBdn5GfGVZqawAOSyhmgULzQ2v4FADDAnRqG+gP6OVJwuJ5gZAAWPIcHuPGEtutr9GlNnYqYzAeX6tT99b9SGYMyw6pgeBW0bwVWMLuDrTu69nd/Sw54R5/hAwf3tlS+s6Hx731XH+Ih5Xm0OzVN92aiozg3Cf0x1XGeL82RHke1091JYRmkk30GAIvYAUdknuurCq/zfZMAQPEuZujgM95wEvp30WUA6IbqdP8Duv+Lqiq56UGkkMQUAQGpHDnqt2uqtdN0JaKVO5GMzMZPjSmgO2XcO8SMTMvW5X+D6r9fzeoPY2M6+OB9Vd57V3lMbS9FPlhdVbAOWFD7cXc3IWmKrmTkj01xjKlIB4NMhoPXYZoPAB6d/fIF7kUxmwXsGr89Dxh8xlvAFDPof5TkmU4zsZABxhckAKIdIGCwSdilYG8QJgwyEXp5HzCOBMDlS7w+Roy5K8h6Y2kmAQeIB1OTkVEF19Hy2ir6Z7zh/OWtLR3g/jYJfDbB8m0M8iaJkO2vkkW36L1Eob45OOPVX2SkjWcAOKViKg0zJlWan+K9iWdN0H53HLAwy8AkhKkG85N8nu8Z4fNI1YHqwTAgJMztR1UwQ0Rebm8SIFIUDgh9JpPn8IBnXNguGJr50xQwlFb/N7/BBc9rFF84YNYfiegRJ7h02J/F0LLTckf4rTSUHh2C3sPa6+ujgwnm/7AKozRhdEQuINnS5U+m5VGQ249fMfrcdEL7yW75mHiRqeLAOqeH92hmACPdOIywKZEcktNP5hgmvVpt4ymVxpkqKY6h0WfrcTnBH+KH7eLoYN83vo4EFjTy198hB7x4tA25uBDZhEbnJQN5WM4ISRO2hVMEn8EBFQfidM+6DaWTI4xoK5zXTds9FNWDy/eQAeh6sblFxaaWSAp+V5cK7d0woU+5HljNzpJHCn4KAzUG9THpJpAl7DFGBcjymX55GI1HB0ynJUZPrwEApUeMATdffL0tkuKetPXowZWaqJuRVtHvdh3Pe3ujrhU6uiJ9F1rbVOyn26NfJDubVAGPDq/5nLtzqUrF1lblyRfFNlIsIATJdCSNHEBZbijNTjGJkGR2Bt9IKo8Je+Mj2uFzAWP+GQCMIv4c9ODEYGIqygT+5HQEQGV95YUlEJjZjiV1/0IVVAXoYYrCsT+9fFGFtjacHSp34e6MTp9c4fRQFKbmErJ8EqlPAtxpbYbyHXrIyCvymWJ3u+6fO61iRxvAIYEk0Z06zNNcZGPGG3kJjPYnkNZ8Rjs2kifJIQFouGx3ZjBGi5IlPzRnmrTwESxgRjix7QSVG8Tb6CAWz2N2/4d933K8aXi75WrU8U9rqzG0QX10jm72tClfW6td2FHsbIbarSq2NKNzWMGoy7OrGM09Qo432KVPLrzJa0T4zhY9PHeGv9v5LlJiHwBM4RlIwCWB7vUD3jyjmb93Le4DxE5fB6mUXcRNDLEDoBPr/KI5t00BMwgAMMcm2NgkcNkJbMT5PNqsrtxiIcLxj2uKLoXsUugO2cOHqo+gsc3x7Uvn5bVSaPMVFWrqleP45Kc/Ur6hSfnmVgqkw60UTuc9UmqxoVnbb74ZgeSn+/Sw+oIcdg0D0xhQGhn7Qvs0b6e3k2vNRkzewTCNCTuEqBLTKWamYgnKATErPpxm8WCJ8DAKi54GgHXfZnLIPYEK9wGicLTCfUG0dVwAnASLEfR7WHVOXm+7Pj5LEe0tuv/aT9jk6GZLnfJ19SrU1cmLd2i/9rI89J0jmRYbGnD8ThUAINfRpN+/+qoeVV9mIwQAFiEDNNeNj4yQD9gSSxlSJ1623x1nt5lWkbG6b5nBAGAJNGnE/Mkkrst2hUEUTZ9sWvuMIncMvbEcWR7w+CKXhBfS8Qr7QEgwCRdmo8djA8B8Lna06EHVGRUo+P4bP8X0AOLVH2vv8mU59U3a4dFt69Le+SrtXXyLxac1ony+AUk0tsi72qQC5zyC9sUa5AJDtqvOK9/BOBwnC5i3pEZUYOQGM5Pao1ifvBAs2t9ICHO0bbdEvojl4+3aaWjUPvQp9GBAnR24qW1UoGxUIrzYNmaLkT9FisM4KiukNFbggOfHBoAV1mlvjy6+AL0//smPla9p1H+8+kOofll7Fy5pu7pa+eoaffSD72vvHIW11ur+j34oD8D2rzZrH5Dy9fV68MZrfEeddjsa9fEZkwjOjpxtwStifnnGZ2mcFR3GWLZxGbN7bIlm7p7d7+CImaaK5OqindTZpaqv/QXO2qlLf/k1ueRsc1J/DBYAQkDHAwLS0Le/BSDXooxwbAAo3gPsP1rh1XVyoHru7Hn98ft/g+6rlLvC0Vgt5yJgnD+j3GU8orOekXdF+5xbaEIejfVIo1YPzr3J8yZ5eMo2E8G3KcBKXGS8ekwOL0PoQsoPMUlLtxaEnvSTH5KYu9XDQnbc63/h841Z++j3UwOg9lLk4k5Tnf79H/5eORYaB3N8fOGCcjDBin906S1G45Vo1udrkEYzBbcy93m+XXUW+uMNTc365C3OMwmTIYoEJQtVJoGCFY2X+MP8zZ0vn//LKGUYiWl2jNTxGfzCAPjZNIbWpoevvxZ1ba/qgvbqa6E0YLRhgLX1FNGEFC7qd698VznOyaHzj37wivIXOaemlilRCzBssNVvaa+NzMDe/xjg7M5QMMoUGKf7eFlk6KTax+QGi9JmivtDKZXZSm3DDAhJL1zQcb/AwV88ws4Dxlrk9tyMKVyhw+0YG9mg0MrdqfpmAKlBDsgDKTw5fVa5q8gFKeRZ2z086xFA+YQjp4voyx2nKF8w712SpdvPvUP2C48R7zERdtsbid42FVjKACtgSy1z46Y8/+w2etx6jn1+saUd2jZHI9Azd2ehKTRdRcf8TcQtMPbcq1eVY7d3LuEDZ2DARQ7kkYMV+dorKmKETktHNPcLFO1wF8jidLQScz/QxQhD7mQHhLlwalwObDAgwimyjuUc1n2frTfgf7uOXcCLfiBvhmvG20jBfZ1kABJfMwXXMeMxtEJzQ8SM/CXozjQwieSrGI/ct4xkAlsMwL1GzmWkudZRW7PRvRtnxA7zyFbpMAHyA/+7TBkbWKRCS7eEI59sUGQdNym8aD3H/rxDUHHI7pbbi+zxFmIs2trjdr0V10Yguhp1Og8DCgBjf7sWeeOtykH9/FW2P7vnl6brtjVSbGizn4gdZZghmIAX2DYYMg2cAe5zRJsl53D4GKOH/ossSP8Dr+Y6weJLG/sAAAAASUVORK5CYII="> </dd> <dt>Title</dt> <dd>Piggy</dd> <dt>Description</dt> <dd>Piggy suit</dd> <dt>Added By</dt> <dd>goldsnacks</dd> <dt>Added On</dt> <dd>2010-10-03</dd> <dt>Votes</dt> <dd>1</dd> </dl>

282.066667

5,110

0.94623

yue_Hant

0.504512

e94f82cc6d0c99d626304d9632e321ebc7b63940

3,201

md

Markdown

powerapps-docs/maker/model-driven-apps/design-custom-business-apps-using-app-designer.md

ganesh-sanap/powerapps-docs

84cfeecd64e9e0d3e32c783432aa2cda0907c439

[ "CC-BY-4.0", "MIT" ]

null

powerapps-docs/maker/model-driven-apps/design-custom-business-apps-using-app-designer.md

ganesh-sanap/powerapps-docs

84cfeecd64e9e0d3e32c783432aa2cda0907c439

[ "CC-BY-4.0", "MIT" ]

null

powerapps-docs/maker/model-driven-apps/design-custom-business-apps-using-app-designer.md

ganesh-sanap/powerapps-docs

84cfeecd64e9e0d3e32c783432aa2cda0907c439

[ "CC-BY-4.0", "MIT" ]

null

--- title: "Design model-driven apps by using the app designer | MicrosoftDocs" description: Learn how to design model-driven apps ms.custom: "" ms.date: 06/27/2018 ms.reviewer: "" ms.service: powerapps ms.suite: "" ms.tgt_pltfrm: "" ms.topic: "get-started-article" applies_to: - "Dynamics 365 (online)" - "Dynamics 365 Version 9.x" - PowerApps ms.assetid: aa6aca00-f95a-4f06-bec4-18b427b4618c ms.author: matp manager: kvivek author: Mattp123 caps.latest.revision: 17 topic-status: Drafting search.audienceType: - maker search.app: - PowerApps - D365CE --- # Design model-driven apps by using the app designer With Power Apps, model-driven apps are comprised of components such as tables, dashboards, forms, views, charts, and business processes. The app designer helps you bring together all these components quickly. Its tile-based information structure and simplified interface make the process of building an app much easier, and you can create apps that are specific to your business roles and functions without having to write any code. Each app that you create can have its own site map with the integrated and easy-to-use site map designer. Just drag and drop areas, groups, and subareas to the canvas. Components that you select in the site map are also added as tables in the app designer. You can add or remove tables as necessary, and also add other components. Once you're done adding components, you can validate your app to check if you have missed adding any required components, add those, and then publish the app for users. The following table shows the steps you'll take to create an app. |Step|Description|Related topics| |----------|-----------------|--------------------| |![Step 1](media/walkthrough-green-1.png "Step 1")|Define app properties.|[Create or edit an app](create-edit-app.md)| |![Step 2](media/walkthrough-green-2.png "Step 2")|Define navigation for an app using the site map designer.|[Create a site map for an app](create-site-map-app.md)| |![Step 3](media/walkthrough-green-3.png "Step 3")|Apps are composed of components like dashboards, tables, business process flows, forms, views, and charts. Include the required ones in your app by using the app designer.|[Add or edit app components](add-edit-app-components.md)| |![Step 4](media/walkthrough-green-4.png "Step 4")|Check your app for any required components you haven't added. After all required components are added make the app available for use. |[Validate and publish an app](validate-app.md)| |![Step 5](media/walkthrough-green-5.png "Step 5")|Give users access to the apps you created by using security roles.|[Share a model-driven app](https://docs.microsoft.com/powerapps/maker/model-driven-apps/share-model-driven-app)| ## Supported web browsers For information about the supported web browsers to use with the app designer and site map designer, see [Supported web browsers and mobile devices](/power-platform/admin/supported-web-browsers-and-mobile-devices). ### Next steps [Build your first model-driven app from scratch](https://docs.microsoft.com/powerapps/maker/model-driven-apps/build-first-model-driven-app)

55.189655

298

0.747266

eng_Latn

0.99126

e94fc55c5df96f3c2880c5542a9a22044646e685

4,685

md

Markdown

README.md

alessandroturrin/SQL_tasble_generator

ab7b24e6a9737b8a784e1820bb4c30b8434b7ffc

[ "Apache-2.0" ]

3

2021-04-25T16:38:01.000Z

2021-04-26T15:49:20.000Z

README.md

alessandroturrin/SQL_tasble_generator

ab7b24e6a9737b8a784e1820bb4c30b8434b7ffc

[ "Apache-2.0" ]

null

README.md

alessandroturrin/SQL_tasble_generator

ab7b24e6a9737b8a784e1820bb4c30b8434b7ffc

[ "Apache-2.0" ]

1

2021-04-29T14:59:00.000Z

# SQL_table_generator LIBRERIA PER LA DEFINIZIONE E LA CREAZIONE DI DATABASE IN LINGUAGGIO SQL @INFORMAZIONI SULLA LIBRERIA Libreria utilizzata per la creazione di attributi random di un database.</br> E' possibile definire mediante input da tastiera lo schema del database.</br> Una volta definito lo schema, il software genera in automatico determinati valori, a seconda dei dati forniti in input.</br> Per lo schema, vengono richieste le seguenti informazioni:</br> 1)Nome database</br> 2)Numero di tabelle del database</br> 2.1)Nome tabella</br> 2.2)Numero di attributi della tabella</br> 2.2.1)Nome dell'attributo</br> 2.2.2)Specifiche dell'attributo:</br> 2.2.2.1)Per il tipo 'Char' è richiesta la dimensione</br> 2.2.2.2)Per il tipi 'Decimal' sono richieste la precisione e la scala</br> 2.2.2)Tipo dell'attributo ['Int','Char','Decimal',Date']</br> 2.2.3)Chiave primaria [Y/N] (non disponibile per il tipo 'Date')</br> 2.2.3)Reference key[Y/N]</br> 2.2.3.1)Tabella di riferimento</br> 2.2.3.2)Chiave di riferimento</br> Per ulteriori informazioni riguardanti i tipi di dato, fare riferimento al paragrafo '@DETTAGLI TIPI DI DATO'.</br> E' consigliabile impostare tutte le chiavi primarie come Char e non come int.</br> @DETTAGLI COMANDI</br> #public String create_database(String directory, String fileName)</br> Riceve come parametri la directory del file di output (con aggiunta finale di '/' a carico dell'utente) e il nome del file.</br> Sono di richiesti in input mediante System.in gli inserimenti dei seguenti dati:</br> 1)numero di tabelle da generare;</br> 2)per ogni attributo vengono richiesti nome, tipo, (chiave primaria,) tabella e chiave di riferimento.</br> Tipi di attributo disponibili: Int, Char, Decimal, Date;</br> 3)per ogni tabella, le caratteristiche di ciascun attributo;</br> Il software riconosce autonomamente la presenza di determinati tipi di attributi assegnando così, in modo randomico, determinati valori selezionati da una serie di elenchi predefiniti, così da poter rendere la generazione delle varie tabelle quanto più realistica possibile.</br> I dati generati vengono stampati su file.</br> </br> #public void create_database()</br> Sono di richiesti in input mediante System.in gli inserimenti dei seguenti dati:</br> 1)numero di tabelle da generare;</br> 2)per ogni attributo vengono richiesti nome, tipo, (chiave primaria,) tabella e chiave di riferimento.</br> Tipi di attributo disponibili: Int, Char, Decimal, Date;</br> 3)per ogni tabella, le caratteristiche di ciascun attributo;</br> Il software riconosce autonomamente la presenza di determinati tipi di attributi assegnando così, in modo randomico, determinati valori selezionati da una serie di elenchi predefiniti, così da poter rendere la generazione delle varie tabelle quanto più realistica possibile.</br> I dati generati vengono stampati a video.</br> </br> #public static void info()</br> Stampa a video il presente modulo di utilizzo.</br> </br> #public static void info(String directory)</br> Riceve come parametri la directory del file di output (con aggiunta finale di '/' a carico dell'utente) e il nome del file.</br> Stampa successivamente il presente modulo di utilizzo.</br> </br> </br> @DETTAGLI TIPI DI DATO</br> CHAR</br> 1)Per la dimensione, sono consigliabili i seguenti accorgimenti:</br> 1.1)Se il char è una chiave primaria, il programma genera in automatico il valore della chiave secondo un ordine crescente. La chiave segue il formato CN, dove C è il primo char del nome dell'attributo, mentre</br> N è un numero crescente, il cui conteggio è a carica del software.</br> La dimensione consigliata è 5.</br> 2.2)Se il char non è una chiave primaria, le seguenti keywords vengono riconosciute:</br> -[Citta|City]</br> -[Nome|Name]</br> -[ID]</br> -[Indirizzo|Address]</br> -[Sport]</br> -[Nazione|Nation]</br> -[Lingua|Language]</br> -[Film|Movie]</br> -[Genere|Genre]</br> -[Tipodiutente|UserType]</br> In caso i dati forniti in input non dovessero corrispondere a nessuna keyword, il software genera in automatico un valore random da inserire nella tabella.</br> La dimensione consigliata è 20.</br> </br> </br> @NOTE E' consigliabile impostare tutte le chiavi primarie come Char e non come int.</br> Non sono momentaneamente stati aggiunti i controlli per tabelle con reference keys(potrebbero esserci valori duplicati), pertanto si consiglia di utilizzare la presente libreria con le dovute cautele.</br> </br> </br> @AUTORE</br> Alessandro Turrin, 21/Apr/2021</br>

55.117647

279

0.738527

ita_Latn

0.996461

e94ff67156e263af8ac0b1dc0c03e8995d627ad3

366

md

Markdown

README.md

Matan18/BalleBot

5d9564de2b54eca1e2afe73251ed7a3f195b0d7f

[ "MIT" ]

1

2021-09-03T04:15:32.000Z

README.md

Matan18/BalleBot

5d9564de2b54eca1e2afe73251ed7a3f195b0d7f

[ "MIT" ]

null

README.md

Matan18/BalleBot

5d9564de2b54eca1e2afe73251ed7a3f195b0d7f

[ "MIT" ]

null

# Balle Bot Discord bot for the Rafaella Ballerini server. ## Table of contents * [Setup](#setup) ## Setup To run this project you'll need `yarn` or `npm`, just follow the steps below. ``` $ cd ../lorem $ npm install $ npm start ``` ## Como você pode adicioná-la? ## Tecnologias utilizadas ## Requisitos ## Como rodar o projeto ## Style Guide ## Alteração

13.071429

77

0.677596

por_Latn

0.543548

e9503a9e233cfb3d7e83c29349cdf28f330a1162

372

md

Markdown

NEWS.md

ReportMort/googlesites

b4af059d0f8e27bad418f185eeee2c9e59c8ace6

[ "MIT" ]

4

2019-04-02T07:30:34.000Z

2021-03-14T10:05:12.000Z

NEWS.md

ReportMort/googlesites

b4af059d0f8e27bad418f185eeee2c9e59c8ace6

[ "MIT" ]

null

NEWS.md

ReportMort/googlesites

b4af059d0f8e27bad418f185eeee2c9e59c8ace6

[ "MIT" ]

2

2020-12-08T15:54:33.000Z

2021-02-12T23:41:46.000Z

## googlesites 0.1.0.9000 ### Features * Nothing Yet! ### Bug Fixes * Nothing Yet! --- ## googlesites 0.1.0 [release](https://github.com/StevenMMortimer/googlesites/releases/tag/v0.1.0) ### Features * Basic Site Manipulation: * `add_html_page()` * `find_content()` * `upload_file_to_site()` * `delete_content()` ### Bug Fixes * None.

14.307692

98

0.615591

yue_Hant

0.508976

e950a6bc9391e55adc73502de01500c0b4d8eff8

21

md

Markdown

CONTRIBUTING.md

StephanYorchenko/such-a-lovely-js

e39b0a894a99ce243f8b505145e777a78aed0043

[ "MIT" ]

9

2021-04-20T11:58:58.000Z

2021-06-06T18:30:40.000Z

CONTRIBUTING.md

StephanYorchenko/such-a-lovely-js

e39b0a894a99ce243f8b505145e777a78aed0043

[ "MIT" ]

18

2021-04-07T14:33:42.000Z

2021-06-10T07:48:07.000Z

CONTRIBUTING.md

StephanYorchenko/such-a-lovely-js

e39b0a894a99ce243f8b505145e777a78aed0043

[ "MIT" ]

3

2021-05-28T18:26:51.000Z

2021-06-07T10:51:16.000Z

PLEASE CONTRIBUTE!!!

10.5

20

0.761905

kor_Hang

0.799157

e9511ae6a0c5abf7b77c19cb98c2a6fc0e81bf2b

6,649

md

Markdown

README.md

creativeprogramming/compass-recipes

ab395720c035edcef10fbf1cf81a4cb7185b0e2b

[ "MIT" ]

1

2019-06-12T19:55:17.000Z

README.md

creativeprogramming/compass-recipes

ab395720c035edcef10fbf1cf81a4cb7185b0e2b

[ "MIT" ]

null

README.md

creativeprogramming/compass-recipes

ab395720c035edcef10fbf1cf81a4cb7185b0e2b

[ "MIT" ]

null

# [Compass Recipes](http://compass-recipes.moox.fr/) [![Build Status](https://secure.travis-ci.org/MoOx/compass-recipes.png)](http://travis-ci.org/MoOx/compass-recipes) A series of Compass and Sass mixins and functions for creating delicious CSS effects. _Compass Recipes is currently under active development. While it's being already used on multiple projects (even in production), you may encounter some issues. Please try it out in a project, and [make suggestions](https://github.com/MoOx/compass-recipes/issues/new) or [report bugs](https://github.com/MoOx/compass-recipes/issues) ! Your feedback matters._ ## [Online Demos](http://compass-recipes.moox.fr/tests/recipes/) If you want to view the Sass(scss) source of a demo, remember to find the appropriate `.scss` file of the deserved `s.css` (e.g. : open it from the source & switch extension). ## Availables Recipes * **[Backgrounds](http://compass-recipes.moox.fr/tests/recipes/background/)** - Background patterns, gradients. * **[Color](http://compass-recipes.moox.fr/tests/recipes/color/)** Variables Names, advanced color functions like `brightness()` & color scheme functions * **[Effects](http://compass-recipes.moox.fr/tests/recipes/effect/)** - Visual effects like `glass`, `bevel`, `cutout` or `ribbon` * **[Form skins](http://compass-recipes.moox.fr/tests/recipes/form/skin/)** - Only one at the moment. Please add yours :) * **[Icon Fonts](http://compass-recipes.moox.fr/tests/recipes/icon-font/)** - Includes icon fonts helper and a few open source fonts as a compass extension ([more info](https://github.com/MoOx/compass-recipes/blob/master/templates/icon-fonts/README.md)) * **[Image](http://compass-recipes.moox.fr/tests/recipes/image/)** - More image mixins (& functions) than Compass deserve (dimensions, inline, simple spriting) * **[Layout](http://compass-recipes.moox.fr/tests/recipes/layout/)** - Vertical centering and box layout shortcuts. * **[Media queries](http://compass-recipes.moox.fr/tests/recipes/media-queries/)** - Shortcuts for media queries. * **[Shadows](http://compass-recipes.moox.fr/tests/recipes/shadow/)** - A wide collection of shadows which use pseudo elements to create fold effects, etc. * **[Shapes](http://compass-recipes.moox.fr/tests/recipes/shape/)** - Geometric and iconic shapes, created only with CSS * **[UI](http://compass-recipes.moox.fr/tests/recipes/ui/)** Lots of element styling for loader, menu, overlay, separator, tooltip, etc. * **[Utilities](http://compass-recipes.moox.fr/tests/recipes/utilities/)** Very usefull utilities, trick, hacks * [View other potential icoming items](https://github.com/MoOx/compass-recipes/issues?labels=enhancement%2Cfeature) ## Installation [Compass Recipes is available as a gem on RubyGems.org](https://rubygems.org/gems/compass-recipes), so installation is quite easy. ```shell (sudo) gem install compass-recipes ``` *If you want all latests recipes, you can just checkout the recipes (or download as zip) and add '{your-path-here-or-./}compass-recipes/stylesheets' using `additional_import_paths` or `add_import_path` (see [Compass configuration reference](http://compass-style.org/help/tutorials/configuration-reference/)). More informations on the [Wiki](https://github.com/MoOx/compass-recipes/wiki)* ## Usage When compass-recipes installed, you just need to require the compass plugin in your project ```ruby require 'compass-recipes' ``` Then you can include some recipes like this ```scss @import "recipes/shape/polygon/triangle"; .my-triangle { @include triangle; } ``` Like Compass does, you can include all recipes in a folder like this ```scss @import "recipes/shape"; .my-triangle { @include triangle; } .my-square { @include square; } ``` ## Support/Community Compass Recipes has for now a little community because this projet is (for now) only at the beginning. [@Compass_Recipes](https://twitter.com/#!/Compass_Recipes) on _Twitter_ is a great place to ask very short questions that you want answered quickly. There is also an IRC channel, **#compass-recipes** on _irc.freenode.net_. Feel free to ping @MoOx if he’s there to get his attention quickly. If there’s no one on **#compass-recipes**, you can try the **#compass** or maybe the **#sass** channel on IRC. If you have a longer question (or no one’s around on IRC at the moment), drop a mail at [compass-recipes@moox.fr](mailto:compass-recipes@moox.fr). You’ll usually get a response within a couple hours or so. ## Open to All If you have a nifty CSS trick that makes sense to be abstracted (and isn't already in another Github repo), please fork and submit a pull request. Note: If you are not the author of the CSS trick, you must get their permission before adding. ## Fonts All fonts are repackaged using [Fontsquirrel](http://www.fontsquirrel.com/fontface/generator). Licences are distributed with the fonts. ## Build Documentation *You do not need to build documentation for testing your recipes.* *Just run `compass watch/compile` at the root of the repository.* First you need bundle ```bundle install``` Then, to build the gh-pages from the `tests/`, you need to call ```bundle exec rake pages``` This process create the pages & commit them to your gh-pages branch. ## Authors/Maintainers Compass Recipes is maintained by [Maxime Thirouin](http://moox.fr), a french front-end web developer, and [David Kaneda](http://www.davidkaneda.com), previously creative director at [Sencha](http://www.sencha.com). [See all contributors](https://github.com/MoOx/compass-recipes/graphs/contributors) While Maxime and David are the primary project maintainers, most of the core ideas and techniques in the recipes are not from them. Credits & Thanks: * [@chriscoyier](https://github.com/chriscoyier) (shapes & lots of tricks) * [@leaverou](https://github.com/leaverou) (backgrounds patterns) * [@necolas](https://github.com/necolas) (normalize & tricks) * [@simurai](https://github.com/simurai) (awesomes design stuffs) * All of the people who contribute to the recipes (all names should be in each recipes source) ### Additional Resources Some other great CSS/SCSS/design projects for making delicious websites: * [Subtle Patterns](http://subtlepatterns.com/) - Great collection of free background patterns, some of which are not possible with CSS alone. * [Animate.sass](https://github.com/adamstac/animate.sass) - A bevy of pre-defined keyframe animations. * [OMG Text](http://jaredhardy.com/omg-text/) - Some super-rad text effects using text-shadow ## License Copyright (c) 2012 Maxime Thirouin Released under [MIT Licence](http://moox.mit-license.org/)

47.492857

357

0.750038

eng_Latn

0.916894

e951317d6a0842a2c7562d22e43162694e5c18e8

3,088

md

Markdown

src/v3/sketch/prototype/interactions.md

PepperAddict/docs

9fc1e6d7568b03ff031fa0ab779782afe528bbc1

[ "MIT" ]

null

src/v3/sketch/prototype/interactions.md

PepperAddict/docs

9fc1e6d7568b03ff031fa0ab779782afe528bbc1

[ "MIT" ]

null

src/v3/sketch/prototype/interactions.md

PepperAddict/docs

9fc1e6d7568b03ff031fa0ab779782afe528bbc1

[ "MIT" ]

null

--- title: Interactions Intro platform: sketch type: prototype order: 14 --- **Interactions** are **State** **Transitions** triggered by Click, Hover, or Timer **Actions**. ## States - A **State** is a canvas which contains all the layers imported from Sketch - The **Initial State** can be imported from a Sketch **Symbol, Artboard,** or **Group** - All the layers that exists in the **Initial State**, will exists in all other **Keyframes** (but can be hidden) - Layers cannot be added or removed from a **State**, but can be made hidden or visible - You can have as many **States** as you want, but to create an animation you need the **Initial State** and at least one more ### The Initial State * The **Initial State** is the starting point. That means all the layers are positioned as they are positioned in the Sketch document * You cannot change layers size or position or any other property in the **Initial State** * To animate layers movement or resizing, create another **State** and move layers around ![Initial State](https://docs.animaapp.com/images/timeline/terminology/initial-state.png) ![States](https://docs.animaapp.com/images/timeline/terminology/states.png) ### States Left Sidebar * The **States Sidebar** is a list of all the **States**. * In each **State** you can view and select all the sub layers and groups of the **State**. * All the **States** contain exactly the same layers. * The **State** has the same layer hierarchy as imported from the Sketch document. * In each **State** (except the **Initial State**) you can show/hide layers and change their properties, which will result in an animation. ![States Sidebar](https://docs.animaapp.com/images/timeline/terminology/states-sidebar.png) ## Actions - An **Action** is a combination of a **Layer**, an **Event** and a **Target State** - An **Action** is what triggers the transition between two **States** - Each transition contains one or more small animations of the different layers the **States** contain ![Actions Supported](http://f.cl.ly/items/0m392P3Z1E2H081S212B/Actions%20Supported.png) As of now, supported **Events** are: - Mouse Click - Mouse Enter - Mouse Leave - Timer When the user performs the chosen **Event**, a **Transition** is triggered onto the **Target State**. For example, let's say there are 2 states: **initial** and **state1**. If we add an **Action** to the **Button Layer** in the **initial state** with the event '**On Mouse Enter**' and connect it to **state1**, then when the user hovers the mouse on the button, the component will perform a **Transition** to **state1**. ![Adding Actions](http://f.cl.ly/items/0U321N1N0j3i3Y0r1444/[53570823639cec21b5ae615f08443441]_Action.gif) ## Transitions - A **Transition** is an animated transition between two **States** - Each **Transition** contains one or more small animations of the different layers the **States** contain - You can select a **Transition** by clicking the blue arrow between two **States** ![Transition](http://f.cl.ly/items/0p1k1d063k1k3m200c2W/Transition.png)

45.411765

248

0.726036

eng_Latn

0.991876

e951b0d269243f042ac45e2ad0b94297c138084c

1,256

md

Markdown

content/events/2017-edinburgh/program/gerie-owen.md

docent-net/devopsdays-web

8056b7937e293bd63b43d98bd8dca1844eee8a88

[ "Apache-2.0", "MIT" ]

6

2016-11-14T14:08:29.000Z

2018-05-09T18:57:06.000Z

content/events/2017-edinburgh/program/gerie-owen.md

docent-net/devopsdays-web

8056b7937e293bd63b43d98bd8dca1844eee8a88

[ "Apache-2.0", "MIT" ]

461

2016-11-11T19:23:06.000Z

2019-07-21T16:10:04.000Z

content/events/2017-edinburgh/program/gerie-owen.md

docent-net/devopsdays-web

8056b7937e293bd63b43d98bd8dca1844eee8a88

[ "Apache-2.0", "MIT" ]

15

2016-11-11T15:07:53.000Z

2019-01-18T04:55:24.000Z

+++ Talk_date = "" Talk_start_time = "" Talk_end_time = "" Title = "DevOps and Groupthink: An Oxymoron?" Type = "talk" Speakers = ["gerie-owen"] youtube = "ArNt3jKzi0w" slideshare = "https://www.slideshare.net/QualiTest-Group/devops-and-groupthink-an-oxymoron" +++ DevOps teams bring together specialists from disciplines with different views on what is most important which forms the basis for groupthink. All closely-knit teams are susceptible to groupthink, a cultural attitude that implicitly rewards members whose striving for unanimity override their motivation to appraise alternative courses of action. DevOps team members from different specialties may often defer to the expert in a particular realm to solve individual problems. This presentation examines groupthink within devops teams. It draws upon the research of Irving Janus, Daniel Kaheman and Carol Dweck to look at how biases and mindsets contribute to groupthink, and why groupthink leads to poor decision-making. You will learn how groupthink can prevent the DevOps team from achieving its goals of agility and quick corrective action and you will learn to use a combination of defined process and prescriptive actions, as individuals and as a team both internally and externally.

78.5

512

0.808121

eng_Latn

0.998942

e951c05f95e26089c6a9e1965e22b2c652a474f1

66

md

Markdown

interesting-links.md

oopanuga/oopanuga.github.io

bbe17f0ff62951eb9594cdddc652927d1cb74e99

[ "MIT" ]

null

interesting-links.md

oopanuga/oopanuga.github.io

bbe17f0ff62951eb9594cdddc652927d1cb74e99

[ "MIT" ]

null

interesting-links.md

oopanuga/oopanuga.github.io

bbe17f0ff62951eb9594cdddc652927d1cb74e99

[ "MIT" ]

null

--- layout: page title: Interesting links permalink: /links/ ---

9.428571

24

0.681818

eng_Latn

0.634938

e951ca2fdfd1b0a860f28fa7ab6613b46868186c

9,301

md

Markdown

articles/billing-usage-rate-card-overview.md

OpenLocalizationTestOrg/azure-docs-pr15_pt-BR

95dabd136ee50edd2caa1216e745b9f13ff7a1f2

[ "CC-BY-3.0", "CC-BY-4.0", "MIT" ]

1

2018-08-29T17:03:44.000Z

articles/billing-usage-rate-card-overview.md

OpenLocalizationTestOrg/azure-docs-pr15_pt-BR

95dabd136ee50edd2caa1216e745b9f13ff7a1f2

[ "CC-BY-3.0", "CC-BY-4.0", "MIT" ]

null

articles/billing-usage-rate-card-overview.md

OpenLocalizationTestOrg/azure-docs-pr15_pt-BR

95dabd136ee50edd2caa1216e745b9f13ff7a1f2

[ "CC-BY-3.0", "CC-BY-4.0", "MIT" ]

null

<properties pageTitle="Obter ideias para seu consumo de recursos do Microsoft Azure | Microsoft Azure" description="Fornece uma visão conceitual do uso de cobrança do Azure e APIs RateCard, que são usados para fornecer ideias para consumo de recursos do Azure e tendências." services="" documentationCenter="" authors="BryanLa" manager="mbaldwin" editor="" tags="billing"/> <tags ms.service="billing" ms.devlang="na" ms.topic="article" ms.tgt_pltfrm="na" ms.workload="billing" ms.date="08/16/2016" ms.author="mobandyo;bryanla"/> # <a name="gain-insights-into-your-microsoft-azure-resource-consumption"></a>Obter ideias para seu consumo de recursos do Microsoft Azure Clientes e parceiros exigem a capacidade de prever com precisão e gerenciar seus custos do Azure. Como eles movimentem de uma Capex a um modelo de Opex, eles também precisam a capacidade de fazer showback versus análise de devolução, bem como fornecem fidelidade de modo no estimativa e cobrança, especialmente para implantações de nuvem grande. O uso de recursos do Azure e APIs de cartão de taxa discutido no endereço neste artigo essas necessidades, permitindo que novas ideias para seu consumo de recursos Azure. ## <a name="introducing-the-azure-resource-usage-and-ratecard-apis"></a>Apresentando o uso do recurso Azure e APIs do RateCard O uso de recursos do Azure e RateCard APIs são implementadas como um provedor de recursos, como parte da família de APIs expostas pelo Resource Manager do Azure. ### <a name="azure-resource-usage-api-preview"></a>Uso do recurso Azure API (prévia) Clientes e parceiros podem usar a API de uso de recursos do Azure para obter seus dados de consumo Azure previsto. Os recursos incluem: - **Controle de acesso baseado em função do azure** - clientes e parceiros pode configurar suas políticas de acesso no [portal do Azure](https://portal.azure.com) ou por meio de [cmdlets do PowerShell do Azure](powershell-install-configure.md) para especificar quais usuários ou aplicativos podem obter acesso aos dados de uso da assinatura. Os chamadores devem usar tokens padrão do Active Directory do Azure para autenticação. O chamador também deve ser adicionado à função Leitor, proprietário ou colaborador para obter acesso a dados de uso para uma assinatura Azure específica. - **Por hora ou agregações diária** - chamadores podem especificar se desejam que seus dados de uso Azure em compartimentos de memória diários ou classificações por hora. O padrão é diário. - **Metadados da instância fornecido (inclui marcas de recurso)** – detalhes de nível de instância como o uri do recurso totalmente qualificado (/subscriptions/ {id da assinatura} / …), junto com o recurso marcas de recursos e informações de grupo serão fornecidas na resposta. Isso ajudar os clientes de forma determinista e alocar programaticamente uso pelas marcas, para casos de uso como charging cruzado. - **Metadados de recurso fornecidos** - detalhes do recurso como o nome do medidor, medidor categoria, medidor subcategoria, unidade e região também serão passados na resposta, dar os chamadores um melhor entendimento do que foi consumida. Estamos também trabalhando para alinhar terminologia de metadados do recurso em portal do Azure, uso Azure CSV, EA CSV e outras experiências público, para permitir que os clientes correlação dados em experiências de cobrança. - **Uso para todos os tipos de oferta** – dados de uso serão acessíveis para todos oferecem tipos incluindo pré-pago, MSDN, compromisso monetário, crédito monetário e EA entre outros. ### <a name="azure-resource-ratecard-api-preview"></a>Recurso Azure RateCard API (prévia) Clientes e parceiros podem usar a API do Azure recurso RateCard para obter a lista de recursos Azure disponíveis, juntamente com estimado preços informações para cada. Os recursos incluem: - **Controle de acesso baseado em função do azure** - clientes e parceiros pode configurar suas políticas de acesso no [portal do Azure](https://portal.azure.com) ou por meio de [cmdlets do PowerShell do Azure](powershell-install-configure.md) para especificar quais usuários ou aplicativos podem obter acesso aos dados RateCard. Os chamadores devem usar tokens padrão do Active Directory do Azure para autenticação. O chamador também deve ser adicionado à função Leitor, proprietário ou colaborador para obter acesso a dados de uso para uma assinatura Azure específica. - **Suporte para pré-pago, MSDN, compromisso monetário e crédito monetário oferece (EA sem suporte)** - este API fornece informações de taxa de nível de oferta Azure, versus nível de assinatura. O chamador desta API deve passar as informações de oferta para obter taxas e detalhes do recurso. Como EA ofertas personalizou taxas por inscrição, estamos incapaz de oferecer as taxas EA neste momento. ## <a name="scenarios"></a>Cenários Aqui estão alguns dos cenários que são feitos possíveis com a combinação de uso e as APIs RateCard: - **Azure passam durante o mês** - os clientes podem usar o uso e RateCard APIs em combinação para obter ideias melhores para seu nuvem passam durante o mês, analisando as classificações de horários e diárias das estimativas de uso e encargo. - **Configurar alertas** – clientes e parceiros pode configurar alertas baseados em monetário ou recurso em seu consumo de nuvem obtendo o consumo previsto e estimativa de encargo utilizando o uso e a API de RateCard. - **Fatura Predict** – clientes e parceiros possam acessar seu consumo previsto e nuvem gasto e aplicar algoritmos de aprendizado de máquina para prever qual seria sua fatura no final do ciclo de cobrança. - **Análise de custo de pré-consumo** – cliente pode também usar a API RateCard prever quanto sua fatura seria se estivessem mover as cargas de trabalho para o Azure, por fornecendo desejado números de uso. Se os clientes têm cargas de trabalho existentes em outros nuvens ou nuvens privadas, eles também podem mapear seu uso com o Azure passam de taxas para obter uma melhor estimativa das sua Azure estimado. Isso fornece um modo de exibição aprimorado do que pode ser obtido através do [Azure Calculadora de preços](https://azure.microsoft.com/pricing/calculator/), como (por exemplo) nossos parceiros de cobrança fornecem a capacidade de oferta de tabela dinâmica e comparar/contraste entre os tipos de oferta diferentes além pré-pago, incluindo compromisso monetário e crédito monetário. As APIs também fornecem a capacidade de custo estimativa por região, permitindo que o tipo de hipóteses necessária para tomar decisões de implantação, como recursos implantando em controladores de domínio diferentes do mundo podem ter um impacto direto em custo total. - **Testes de hipóteses** - - Clientes e parceiros podem determinar se seria mais econômico para executar as cargas de trabalho em outra região, ou em outra configuração do recurso Azure. Recurso Azure custos podem ser diferentes com base no Azure região em que estão sendo executados e isso permite que clientes e parceiros obter as otimizações de custo. - Clientes e parceiros também podem determinar se outro tipo de oferta Azure oferece uma melhor taxa em um recurso Azure. ## <a name="partner-solutions"></a>Soluções de parceiros [Uso do Microsoft Azure e RateCard APIs habilitar Cloudyn para fornecer ITFM para clientes que](billing-usage-rate-card-partner-solution-cloudyn.md) descreve a experiência de integração oferecida pelo parceiro do Azure cobrança API [Cloudyn](https://www.cloudyn.com/microsoft-azure/). Este artigo fornece cobertura detalhada das suas experiências, incluindo um vídeo curto que mostra como um cliente do Azure pode usar Cloudyn e APIs de cobrança do Azure para obtenção de informações de ganhos de seus dados de consumo Azure. [Cruiser de nuvem e a integração de API de cobrança do Microsoft Azure](billing-usage-rate-card-partner-solution-cloudcruiser.md) descreve como [da nuvem Cruiser Express para pacote Azure](http://www.cloudcruiser.com/partners/microsoft/) funciona diretamente no portal de WAP, permitindo que os clientes perfeitamente gerenciar os aspectos operacionais e financeiros da seu Microsoft Azure privado ou hospedado público em nuvem de uma única interface de usuário. ## <a name="next-steps"></a>Próximas etapas + Confira a [Referência da API REST Azure cobrança](https://msdn.microsoft.com/library/azure/1ea5b323-54bb-423d-916f-190de96c6a3c) para obter mais detalhes sobre as duas APIs, que fazem parte do conjunto de APIs fornecidas pelo Resource Manager do Azure. + Se você gostaria de mergulhar diretamente em código de exemplo, confira nossa Microsoft Azure cobrança API amostras de código em [Amostras de código do Azure](https://azure.microsoft.com/documentation/samples/?term=billing). ## <a name="learn-more"></a>Saiba Mais + Consulte o artigo de [Visão geral do Gerenciador de recursos do Azure](azure-resource-manager/resource-group-overview.md) para saber mais sobre o Gerenciador de recursos do Azure. + Para obter informações adicionais sobre o pacote de ferramentas necessárias para ajudar a compreender nuvem gastos, consulte o artigo Gartner [Guia de mercado para ferramentas de gerenciamento de TI financeiro (ITFM)](http://www.gartner.com/technology/reprints.do?id=1-212F7AL&ct=140909&st=sb).

114.82716

1,061

0.796366

por_Latn

0.999721

e952b5ad21ed0704fcebf6a7b903c32017a763c0

2,999

md

Markdown

storage-resize-images/CHANGELOG.md

Takuya-Miyazaki/extensions

541d828fc3232b26d31f5f6bdf18d1631efa57dd

[ "Apache-2.0" ]

null

storage-resize-images/CHANGELOG.md

Takuya-Miyazaki/extensions

541d828fc3232b26d31f5f6bdf18d1631efa57dd

[ "Apache-2.0" ]

null

storage-resize-images/CHANGELOG.md

Takuya-Miyazaki/extensions

541d828fc3232b26d31f5f6bdf18d1631efa57dd

[ "Apache-2.0" ]

null

## Version 0.1.17 docs - Adds documentation that explains which content types are supported, and shows how to set content type explicitly (#534) ## Version 0.1.16 feature - Adds support for absolute paths restrictions for Storage Resize Image (#427) ## Version 0.1.15 fixed - extension bug. File name incorrect if non-standard file name (#477) ## Version 0.1.14 feature - Added a "delete only on success" option to the `DELETE_ORIGINAL_FILE` param (#479) ## Version 0.1.13 feature - Add new parameter to optionally convert each uploaded image to a different image content-type (PR #483) ## Version 0.1.12 fixed - ignore gzipped images (PR #417) feature - Add new Cloud Functions locations. For more information about locations and their pricing tiers, refer to the [location selection guide](https://firebase.google.com/docs/functions/locations). ## Version 0.1.11 feature - Update Cloud Functions runtime to Node.js 10. ## Version 0.1.10 fixed - A fresh token is now generated for each resized image. (Issue #323, PR #351) ## Version 0.1.9 changed - If the original image is a vector image, the extension does not resize it. (Issue #326, PR #329) fixed - Replaced `mkdirp-promise` with `mkdirp` because `mkdirp-promise` is deprecated. (PR #266) fixed - If the original image is smaller than the specified max width and height, the extension does not enlarge it or resize it. (Issue #337, PR #338) ## Version 0.1.8 fixed - Resized images now maintain the same orientation as the original image. (Issue #290) ## Version 0.1.7 fixed - Resized images now render in the Firebase console. (Issue #140) fixed - The Sharp cache is now cleared so that the latest image with a given file name is retrieved from the Storage bucket. (Issue #286) ## Version 0.1.6 fixed - Switched ImageMagick for Sharp library to support webp format. (Issue #199) ## Version 0.1.5 fixed - The original, uploaded image's MIME type must now always be specified in the `Content-Type` header. (Issue #175) ## Version 0.1.4 fixed - Fixed bug where name of resized file was missing original name if there was no file extension. (issue #20) fixed - Fixed "TypeError: Cannot set property 'resizedImage' of undefined". (issue #130) fixed - Fixed bug where some valid bucket names were rejected during configuration. (issue #27) ## Version 0.1.3 feature - Automatically copy the following metadata, if present, from the original image to the resized image(s): `Cache-Control`, `Content-Disposition`, `Content-Encoding`, `Content-Language`, `Content-Type`, and user-provided metadata (except Firebase storage download tokens). Note that you can configure your extension to overwrite the Cache-Control value for the resized image(s). ## Version 0.1.2 feature - Added new param for deleting the original image. ## Version 0.1.1 fixed - Fixed bug where certain edge cases led to already resized image being resized again. (issue #7) ## Version 0.1.0 Initial release of the _Resize Images_ extension.

35.282353

385

0.749583

eng_Latn

0.993524

e953ff74ffd0ce08b188964874d7322d6c1c87ca

420

md

Markdown

docs/src/plotting_functions/boxplot.md

kolia/AbstractPlotting.jl

ad88c40522a73cb446cd5fecbdaeb8871a6d0bfa

[ "MIT" ]

95

2018-05-31T15:00:02.000Z

2022-01-25T03:27:01.000Z

docs/src/plotting_functions/boxplot.md

kolia/AbstractPlotting.jl

ad88c40522a73cb446cd5fecbdaeb8871a6d0bfa

[ "MIT" ]

460

2018-07-12T13:10:49.000Z

2021-06-01T19:59:23.000Z

docs/src/plotting_functions/boxplot.md

kolia/AbstractPlotting.jl

ad88c40522a73cb446cd5fecbdaeb8871a6d0bfa

[ "MIT" ]

92

2018-08-30T22:03:34.000Z

2021-12-13T23:22:42.000Z

# boxplot ```@docs boxplot ``` ### Examples ```@example using CairoMakie CairoMakie.activate!() # hide AbstractPlotting.inline!(true) # hide xs = rand(1:3, 1000) ys = randn(1000) boxplot(xs, ys) ``` ```@example using CairoMakie CairoMakie.activate!() # hide AbstractPlotting.inline!(true) # hide xs = rand(1:3, 1000) ys = randn(1000) dodge = rand(1:2, 1000) boxplot(xs, ys, dodge = dodge, show_notch = true) ```

13.548387

49

0.669048

eng_Latn

0.284716

e95502ea2b70ca33f6bce6a9ac71409e3ec31ed6

766

md

Markdown

src/pages/blog/2017/12/22-02.md

Neos21GitHub/neo.s21.xrea.com

8b867683273ba36cf7cccd6ff0037e60f7243599

[ "MIT" ]

null

src/pages/blog/2017/12/22-02.md

Neos21GitHub/neo.s21.xrea.com

8b867683273ba36cf7cccd6ff0037e60f7243599

[ "MIT" ]

null

src/pages/blog/2017/12/22-02.md

Neos21GitHub/neo.s21.xrea.com

8b867683273ba36cf7cccd6ff0037e60f7243599

[ "MIT" ]

null

--- title : Uglify-JS って ES2015 の圧縮できないの？ → Uglify-ES を使う created : 2017-12-22 last-modified: 2017-12-22 header-date : true path: - /index.html Neo's World - /blog/index.html Blog - /blog/2017/index.html 2017年 - /blog/2017/12/index.html 12月 hidden-info: original-blog: Corredor --- Uglify-JS で ES2015 のコードを圧縮しようとしたらエラーが出た。よくよく調べたら、「Uglify-JS」というパッケージでは ES2015 の対応はせず、別途__「Uglify-ES」__というパッケージで提供しているということだった。 - [uglify-es](https://www.npmjs.com/package/uglify-es) ものは試し。 ```bash # コマンドが同じなので uglify-js はアンインストールしておく $ npm uninstall -g uglify-js # 今回はグローバルインストールにしたがローカルインストールでも特に変わりなし $ npm install -g uglify-es ``` 実行コマンドは同じ _`uglify-js`_ を使用する。オプションの類も同じなので、自分のコードを ES2015 に書き換えたら、使用するパッケージを uglify-js から uglify-es に入れ替えるだけで移行が完了する。

23.9375

118

0.74282

yue_Hant

0.376329

e9563a9f4976976191e00aeaab05fd381756c7c8

3,231

md

Markdown

biztalk/core/how-to-create-or-add-an-artifact.md

cmcclister/biztalk-docs

36a3d4b944e27edff883b8e36e997c7d2af4f497

[ "CC-BY-4.0", "MIT" ]

37

2017-08-28T06:57:52.000Z

2021-07-13T12:16:23.000Z

biztalk/core/how-to-create-or-add-an-artifact.md

cmcclister/biztalk-docs

36a3d4b944e27edff883b8e36e997c7d2af4f497

[ "CC-BY-4.0", "MIT" ]

732

2017-05-18T22:16:15.000Z

2022-03-31T23:10:06.000Z

biztalk/core/how-to-create-or-add-an-artifact.md

isabella232/biztalk-docs

36a3d4b944e27edff883b8e36e997c7d2af4f497

[ "CC-BY-4.0", "MIT" ]

158

2017-06-19T22:47:52.000Z

2022-02-28T06:41:54.000Z

--- description: "Learn more about: How to Create or Add an Artifact" title: "How to Create or Add an Artifact | Microsoft Docs" ms.custom: "" ms.date: "06/08/2017" ms.prod: "biztalk-server" ms.reviewer: "" ms.suite: "" ms.tgt_pltfrm: "" ms.topic: "article" helpviewer_keywords: - "creating, artifacts" - "artifacts, creating" - "applications, artifacts" ms.assetid: fea7487c-b5fa-457f-8c74-a20ea3a6df85 caps.latest.revision: 16 author: "MandiOhlinger" ms.author: "mandia" manager: "anneta" --- # How to Create or Add an Artifact After you create a BizTalk application, you can add file-based artifacts (for example BizTalk assemblies, .NET assemblies, scripts, and certificates) from the file system or add policies from the Rule Engine database. You can also create send ports, send port groups, receive locations, and receive ports within the application. Creating or adding artifacts adds them to the BizTalk Management database. You can then deploy the application and its artifacts as a single entity, as described in [Deploying BizTalk Applications](../core/deploying-biztalk-applications.md). > [!NOTE] > Certain types of artifacts must be unique in a BizTalk application or group. For more information, see [Artifacts That Must Be Unique in an Application or Group](../core/artifacts-that-must-be-unique-in-an-application-or-group.md). For procedures on adding or creating each artifact type, see the following topics: - [How to Create a Send Port](../core/how-to-create-a-send-port2.md) - [How to Create a Send Port Group](../core/how-to-create-a-send-port-group.md) - [How to Create a Receive Port](../core/how-to-create-a-receive-port.md) - [How to Create a Receive Location](../core/how-to-create-a-receive-location.md) - [How to Add a Policy to an Application](../core/how-to-add-a-policy-to-an-application.md) - [How to Add a BizTalk Assembly to an Application](../core/how-to-add-a-biztalk-assembly-to-an-application.md) - [How to Add a Pre- or Post-processing Script to an Application](../core/how-to-add-a-pre-or-post-processing-script-to-an-application.md) - [How to Add a File to an Application](../core/how-to-add-a-file-to-an-application.md) - [How to Add a Certificate to an Application](../core/how-to-add-a-certificate-to-an-application.md) - [How to Add a COM Component to an Application](../core/how-to-add-a-com-component-to-an-application.md) - [How to Add a .NET Assembly to an Application](../core/how-to-add-a-net-assembly-to-an-application.md) - [How to Add a BAM Artifact to an Application](../core/how-to-add-a-bam-artifact-to-an-application.md) - [How to Add a Binding File to an Application](../core/how-to-add-a-binding-file-to-an-application2.md) > [!NOTE] > If the artifact you are adding has a very long path (e.g., the path and file name), the operation to add the artifact to an application may fail. A path can't exceed 260 characters. ## See Also [Creating and Modifying BizTalk Applications](../core/creating-and-modifying-biztalk-applications.md) [How to Add a 64-Bit Artifact to an Application](../core/how-to-add-a-64-bit-artifact-to-an-application.md)

52.112903

572

0.722686

eng_Latn

0.914046

e956b3ca105f2e21d264ca1cfc46ba0d2e8db47a

54

md

Markdown

README.md

redvvelvet/COVID19-prediction-with-Machine-Learning

24be89b7e757becc720a3a83dbf742fbef7df001

[ "MIT" ]

null

README.md

redvvelvet/COVID19-prediction-with-Machine-Learning

24be89b7e757becc720a3a83dbf742fbef7df001

[ "MIT" ]

null

README.md

redvvelvet/COVID19-prediction-with-Machine-Learning

24be89b7e757becc720a3a83dbf742fbef7df001

[ "MIT" ]

1

2021-07-07T23:23:28.000Z

# COVID19-prediction-in-Jakarta-with-Machine-Learning

27

53

0.833333

yue_Hant

0.563221

e9587fc427576b9f393bd2add1c7c0423aa6ecdf

6,356

md

Markdown

README.md

whojr01/bdb-provision

f1ae9e43bd071ad05c9af05b4a1be38b74f1ebf5

[ "MIT" ]

null

README.md

whojr01/bdb-provision

f1ae9e43bd071ad05c9af05b4a1be38b74f1ebf5

[ "MIT" ]

null

README.md

whojr01/bdb-provision

f1ae9e43bd071ad05c9af05b4a1be38b74f1ebf5

[ "MIT" ]

null

# bdb-provision Provisions virtual machines based on the description entered in the VM_Machine.json file. The current initial version supports CentOS/7 as the provisioned OS. The provisioned machine includes a service that updates the ip-address for all virutal machines as a systemD service. The disk provisioning script AddDockerDisk.sh is still under development. Below is the Youtube episodes recorded for the development of the provisioning system. ## Boston Devops Bill Episodes <dl> <dt><a href="https://youtu.be/XN5QoDrZJok">Episode 1</a></dt> <dd> This channel builds a hybrid development/operations framework within a virtual environment with targeted deployments to AWS. </dd> </dl> <dl> <dt><a href="https://youtu.be/GvkckRCHWN8">Episode 2</a></dt> <dd> In this episode of Boston DevOps Bill we begin our journey to create the provisioning utility using Vagrant and VirtualBox.<br><br>I provide a brief install instructions as well as URL's to each component. Once you have completed the installs we'll create a test Vagrantfile and spin up a Virtual environment. </dd> </dl> <dl> <dt><a href="https://youtu.be/FKQeD2JUqE8">Episode 3</a></dt> <dd> The work continues on the provisioning utility and in this installment we create the JSON file that we will use to describe each node.<br><br>Of course I let you with a real cliff hanger [sorry no spoiler alerts], but I can assure you that nobody got hurt while filming this episode. </dd> </dl> <dl> <dt><a href="https://youtu.be/sjV4JdAw-Vs">Episode 4</a></dt> <dd> The saga of provisioning continues as we forge ahead into uncharted JSON keys to join our Vagrantfile with our VM_Machine.json file.<br><br>We'll learn about loops as we build loops to traverse through our defined machines and build loops within loops to handle shares and ports. All in all this is a pound the keys episode!<br><br>Of course I will leave you (not yet) with a real clif hanger [sorry no spoiler alerts], but I can assure you that I was not hurt by the Supervisor today (Yes, I fed her before I started recording). </dd> </dl> <dl> <dt><a href="https://youtu.be/X8iC5Q5lKLg">Episode 5</a></dt> <dd> This episode focuses on testing our Vagrantfile & JSON file together to define VM's as described in the JSON file.<br><br>Today we embark on a journey to create a mechanism to sync IP Addresses across all VM Machines regardless of whether they are defined or not. Please note this is not for the faint of heart as there will be nashing of teeth, lots of rum, and a yo ho ho!<br><br>Another words we're gonna bang some keys and have lots of fun! As usual I will leave you with a cliff hanger! </dd> <dl> <dl> <dt><a href="https://youtu.be/Ay2uxX-PlLg">Episode 6</a></dt> <dd> Today we embark on a journey to create a mechanism to sync IP Addresses across all VM Machines regardless of whether they are defined or not. Please note this is not for the faint of heart as there will be nashing of teeth, lots of rum, and a yo ho ho!<br><br>Another words we're gonna bang some keys and have lots of fun! As usual I will leave you with a cliff hanger! </dd> </dl> <dl> <dt><a href="https://youtu.be/olOagT1yua4">Episode 7</a></dt> <dd>In our last session we ended with the discovery of a severity 1 defect. In this episode we'll take an in depth look at this issue.<br><br>Well, that's great. No contact with the Vagrantfile, a xenomorph may be involved!<br><br>What do you mean *they* cut the power? How could they cut the power, man?<br><br>A xenomorph can do anything if left unchecked.<br><br>That's it, man. Game over, man. Game over!<br><br>Only the brave should continue as we dip into the primordial bits in an attempt resolve the issue. Be warned, Ripply couldn't make it. Only the shadow knows if we can get past this. </dd> </dl> <dl> <dt><a href="https://youtu.be/liwdI4zCsHo">Episode 8</a></dt> <dd> After barely surviving the encounter with the xenomorph we forged on to face new challenges, as we enter the monsters territory of SystemD, with support from Timer and Service Unit who graciously agreed to help.<br><br>The arduous climb up took longer than anticipated, but even with noticiable degradation of visuals towards the end, we pressed on!<br><br>Kindly please be advised, due to recent budget custs, we're unable to provide snacks, during this exciting episode. </dd> </dl> <dl> <dt><a href="https://youtu.be/7xYD9h8kIUI">Episode 9</a></dt> <dd> Well we're forced by the cleaning crew to make this episode a bit shorter so there is no reason to bring snacks. Thank you to those who cleaned up after themselves.<br><br> In this episode we'll be deploying to parts known as we complete the IP Sync component of our provisioning system. Unfortunately due to the large amount of trash left over from the last episode, future (next) episode, will be creating defining storage facilities. </dd> </dl> <dl> <dt><a href="https://youtu.be/uvGcZstc1Ag">Episode 10</a></dt> <dd> This episode we begin creating the provisioning storage script that will create the three types of drives (Standard storage, Logical Volumes, and Thin Provisioned disks) by the Storage system.<br><br>We will clean up the code to our IP Sync system removing the tempfile we created, log entry, and adding ourselves to the VirtualBox group so we don't need to be root to access the admin share. </dd> </dl> <dl> <dt><a href="https://youtu.be/BWY7RyBt7tE">Episode 11</a></dt> <dd> In this episode I highlight Zenoss, Zenoss provides infrasructure management, at any scale as software as a service. Take a look its really cool stuff!<br><br>Afterwards we continue to build out our storage script by developing a better test for drives not in use, adding additional checks for our tuple, and adding the skeleton functions to create the storage drives. </dd> </dl> <dl> <dt><a href="https://youtu.be/CD2wDDe2S4Y">Episode 12</a></dt> <dd> This episode we define the functions drive (For partitioning and formating) a standard drive and lv (For creating a logcial volume). We saved the creation of the thin volume drive routine for the next episode. </dd> </dl>

66.208333

601

0.727816

eng_Latn

0.995978

e959d82577eda9581f6a17d4e7b8ce9af627245f

1,096

md

Markdown

documentation/abnormal_termination/step2/using_diagnostic_report.md

cupofjoakim/diagnostics

014aa9e1fd1a674545f621e48a6b17cb0472eac3

[ "MIT" ]

1

2020-12-01T20:55:13.000Z

documentation/abnormal_termination/step2/using_diagnostic_report.md

cupofjoakim/diagnostics

014aa9e1fd1a674545f621e48a6b17cb0472eac3

[ "MIT" ]

1

2021-03-25T06:39:35.000Z

documentation/abnormal_termination/step2/using_diagnostic_report.md

cupofjoakim/diagnostics

014aa9e1fd1a674545f621e48a6b17cb0472eac3

[ "MIT" ]

null

# Using Diagnostic Report Formerly known as node-report. The report is intended for development, test and production use, to capture and preserve information for problem determination. It includes JavaScript and native stack traces, heap statistics, platform information, resource usage etc. Diagnostic Report can be useful to discover configuration and component version issues with in your process. ## How To //TODO, raw notes from deep dive: 1. Open the generated report (either from file or from console) 2. Take a look to allocation section in the report 3. Look for the old_space - used is high - available is very low 4. Look javascriptStack to see the victim of the memory leak which can be the allocation pattern and source to find what causes it (JavaScript stack trace won’t always point to the right frame, can be confusing) 5. -> see memory related user journeys to identify exact cause ## Useful Links _ https://nodejs.org/api/report.html - https://medium.com/the-node-js-collection/easily-identify-problems-in-node-js-applications-with-diagnostic-report-dc82370d8029

43.84

211

0.790146

eng_Latn

0.995164

e959f4981ed8c8a8243e35587c8f47d4ac8a2cfd

10,116

md

Markdown

docs/HyperflexClusterReplicationNetworkPolicy.md

pktyagi1/intersight-go

1f8bd2aa1b8cbdf35d45068fb113b65ee41df3ed

[ "Apache-2.0" ]

null

docs/HyperflexClusterReplicationNetworkPolicy.md

pktyagi1/intersight-go

1f8bd2aa1b8cbdf35d45068fb113b65ee41df3ed

[ "Apache-2.0" ]

1

2022-03-21T06:28:43.000Z

docs/HyperflexClusterReplicationNetworkPolicy.md

pktyagi1/intersight-go

1f8bd2aa1b8cbdf35d45068fb113b65ee41df3ed

[ "Apache-2.0" ]

2

2020-07-07T15:00:25.000Z

2022-03-21T04:43:33.000Z

# HyperflexClusterReplicationNetworkPolicy ## Properties Name | Type | Description | Notes ------------ | ------------- | ------------- | ------------- **ClassId** | **string** | The fully-qualified name of the instantiated, concrete type. This property is used as a discriminator to identify the type of the payload when marshaling and unmarshaling data. | [default to "hyperflex.ClusterReplicationNetworkPolicy"] **ObjectType** | **string** | The fully-qualified name of the instantiated, concrete type. The value should be the same as the 'ClassId' property. | [default to "hyperflex.ClusterReplicationNetworkPolicy"] **ReplicationBandwidthMbps** | Pointer to **int64** | Bandwidth for the Replication network in Mbps. | [optional] [default to 0] **ReplicationIpranges** | Pointer to [**[]HyperflexIpAddrRange**](HyperflexIpAddrRange.md) | | [optional] **ReplicationMtu** | Pointer to **int64** | MTU for the Replication network. | [optional] [default to 1500] **ReplicationVlan** | Pointer to [**NullableHyperflexNamedVlan**](HyperflexNamedVlan.md) | | [optional] **ClusterProfiles** | Pointer to [**[]HyperflexClusterProfileRelationship**](HyperflexClusterProfileRelationship.md) | An array of relationships to hyperflexClusterProfile resources. | [optional] **Organization** | Pointer to [**OrganizationOrganizationRelationship**](OrganizationOrganizationRelationship.md) | | [optional] ## Methods ### NewHyperflexClusterReplicationNetworkPolicy `func NewHyperflexClusterReplicationNetworkPolicy(classId string, objectType string, ) *HyperflexClusterReplicationNetworkPolicy` NewHyperflexClusterReplicationNetworkPolicy instantiates a new HyperflexClusterReplicationNetworkPolicy object This constructor will assign default values to properties that have it defined, and makes sure properties required by API are set, but the set of arguments will change when the set of required properties is changed ### NewHyperflexClusterReplicationNetworkPolicyWithDefaults `func NewHyperflexClusterReplicationNetworkPolicyWithDefaults() *HyperflexClusterReplicationNetworkPolicy` NewHyperflexClusterReplicationNetworkPolicyWithDefaults instantiates a new HyperflexClusterReplicationNetworkPolicy object This constructor will only assign default values to properties that have it defined, but it doesn't guarantee that properties required by API are set ### GetClassId `func (o *HyperflexClusterReplicationNetworkPolicy) GetClassId() string` GetClassId returns the ClassId field if non-nil, zero value otherwise. ### GetClassIdOk `func (o *HyperflexClusterReplicationNetworkPolicy) GetClassIdOk() (*string, bool)` GetClassIdOk returns a tuple with the ClassId field if it's non-nil, zero value otherwise and a boolean to check if the value has been set. ### SetClassId `func (o *HyperflexClusterReplicationNetworkPolicy) SetClassId(v string)` SetClassId sets ClassId field to given value. ### GetObjectType `func (o *HyperflexClusterReplicationNetworkPolicy) GetObjectType() string` GetObjectType returns the ObjectType field if non-nil, zero value otherwise. ### GetObjectTypeOk `func (o *HyperflexClusterReplicationNetworkPolicy) GetObjectTypeOk() (*string, bool)` GetObjectTypeOk returns a tuple with the ObjectType field if it's non-nil, zero value otherwise and a boolean to check if the value has been set. ### SetObjectType `func (o *HyperflexClusterReplicationNetworkPolicy) SetObjectType(v string)` SetObjectType sets ObjectType field to given value. ### GetReplicationBandwidthMbps `func (o *HyperflexClusterReplicationNetworkPolicy) GetReplicationBandwidthMbps() int64` GetReplicationBandwidthMbps returns the ReplicationBandwidthMbps field if non-nil, zero value otherwise. ### GetReplicationBandwidthMbpsOk `func (o *HyperflexClusterReplicationNetworkPolicy) GetReplicationBandwidthMbpsOk() (*int64, bool)` GetReplicationBandwidthMbpsOk returns a tuple with the ReplicationBandwidthMbps field if it's non-nil, zero value otherwise and a boolean to check if the value has been set. ### SetReplicationBandwidthMbps `func (o *HyperflexClusterReplicationNetworkPolicy) SetReplicationBandwidthMbps(v int64)` SetReplicationBandwidthMbps sets ReplicationBandwidthMbps field to given value. ### HasReplicationBandwidthMbps `func (o *HyperflexClusterReplicationNetworkPolicy) HasReplicationBandwidthMbps() bool` HasReplicationBandwidthMbps returns a boolean if a field has been set. ### GetReplicationIpranges `func (o *HyperflexClusterReplicationNetworkPolicy) GetReplicationIpranges() []HyperflexIpAddrRange` GetReplicationIpranges returns the ReplicationIpranges field if non-nil, zero value otherwise. ### GetReplicationIprangesOk `func (o *HyperflexClusterReplicationNetworkPolicy) GetReplicationIprangesOk() (*[]HyperflexIpAddrRange, bool)` GetReplicationIprangesOk returns a tuple with the ReplicationIpranges field if it's non-nil, zero value otherwise and a boolean to check if the value has been set. ### SetReplicationIpranges `func (o *HyperflexClusterReplicationNetworkPolicy) SetReplicationIpranges(v []HyperflexIpAddrRange)` SetReplicationIpranges sets ReplicationIpranges field to given value. ### HasReplicationIpranges `func (o *HyperflexClusterReplicationNetworkPolicy) HasReplicationIpranges() bool` HasReplicationIpranges returns a boolean if a field has been set. ### SetReplicationIprangesNil `func (o *HyperflexClusterReplicationNetworkPolicy) SetReplicationIprangesNil(b bool)` SetReplicationIprangesNil sets the value for ReplicationIpranges to be an explicit nil ### UnsetReplicationIpranges `func (o *HyperflexClusterReplicationNetworkPolicy) UnsetReplicationIpranges()` UnsetReplicationIpranges ensures that no value is present for ReplicationIpranges, not even an explicit nil ### GetReplicationMtu `func (o *HyperflexClusterReplicationNetworkPolicy) GetReplicationMtu() int64` GetReplicationMtu returns the ReplicationMtu field if non-nil, zero value otherwise. ### GetReplicationMtuOk `func (o *HyperflexClusterReplicationNetworkPolicy) GetReplicationMtuOk() (*int64, bool)` GetReplicationMtuOk returns a tuple with the ReplicationMtu field if it's non-nil, zero value otherwise and a boolean to check if the value has been set. ### SetReplicationMtu `func (o *HyperflexClusterReplicationNetworkPolicy) SetReplicationMtu(v int64)` SetReplicationMtu sets ReplicationMtu field to given value. ### HasReplicationMtu `func (o *HyperflexClusterReplicationNetworkPolicy) HasReplicationMtu() bool` HasReplicationMtu returns a boolean if a field has been set. ### GetReplicationVlan `func (o *HyperflexClusterReplicationNetworkPolicy) GetReplicationVlan() HyperflexNamedVlan` GetReplicationVlan returns the ReplicationVlan field if non-nil, zero value otherwise. ### GetReplicationVlanOk `func (o *HyperflexClusterReplicationNetworkPolicy) GetReplicationVlanOk() (*HyperflexNamedVlan, bool)` GetReplicationVlanOk returns a tuple with the ReplicationVlan field if it's non-nil, zero value otherwise and a boolean to check if the value has been set. ### SetReplicationVlan `func (o *HyperflexClusterReplicationNetworkPolicy) SetReplicationVlan(v HyperflexNamedVlan)` SetReplicationVlan sets ReplicationVlan field to given value. ### HasReplicationVlan `func (o *HyperflexClusterReplicationNetworkPolicy) HasReplicationVlan() bool` HasReplicationVlan returns a boolean if a field has been set. ### SetReplicationVlanNil `func (o *HyperflexClusterReplicationNetworkPolicy) SetReplicationVlanNil(b bool)` SetReplicationVlanNil sets the value for ReplicationVlan to be an explicit nil ### UnsetReplicationVlan `func (o *HyperflexClusterReplicationNetworkPolicy) UnsetReplicationVlan()` UnsetReplicationVlan ensures that no value is present for ReplicationVlan, not even an explicit nil ### GetClusterProfiles `func (o *HyperflexClusterReplicationNetworkPolicy) GetClusterProfiles() []HyperflexClusterProfileRelationship` GetClusterProfiles returns the ClusterProfiles field if non-nil, zero value otherwise. ### GetClusterProfilesOk `func (o *HyperflexClusterReplicationNetworkPolicy) GetClusterProfilesOk() (*[]HyperflexClusterProfileRelationship, bool)` GetClusterProfilesOk returns a tuple with the ClusterProfiles field if it's non-nil, zero value otherwise and a boolean to check if the value has been set. ### SetClusterProfiles `func (o *HyperflexClusterReplicationNetworkPolicy) SetClusterProfiles(v []HyperflexClusterProfileRelationship)` SetClusterProfiles sets ClusterProfiles field to given value. ### HasClusterProfiles `func (o *HyperflexClusterReplicationNetworkPolicy) HasClusterProfiles() bool` HasClusterProfiles returns a boolean if a field has been set. ### SetClusterProfilesNil `func (o *HyperflexClusterReplicationNetworkPolicy) SetClusterProfilesNil(b bool)` SetClusterProfilesNil sets the value for ClusterProfiles to be an explicit nil ### UnsetClusterProfiles `func (o *HyperflexClusterReplicationNetworkPolicy) UnsetClusterProfiles()` UnsetClusterProfiles ensures that no value is present for ClusterProfiles, not even an explicit nil ### GetOrganization `func (o *HyperflexClusterReplicationNetworkPolicy) GetOrganization() OrganizationOrganizationRelationship` GetOrganization returns the Organization field if non-nil, zero value otherwise. ### GetOrganizationOk `func (o *HyperflexClusterReplicationNetworkPolicy) GetOrganizationOk() (*OrganizationOrganizationRelationship, bool)` GetOrganizationOk returns a tuple with the Organization field if it's non-nil, zero value otherwise and a boolean to check if the value has been set. ### SetOrganization `func (o *HyperflexClusterReplicationNetworkPolicy) SetOrganization(v OrganizationOrganizationRelationship)` SetOrganization sets Organization field to given value. ### HasOrganization `func (o *HyperflexClusterReplicationNetworkPolicy) HasOrganization() bool` HasOrganization returns a boolean if a field has been set. [[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md)

39.057915

262

0.816232

eng_Latn

0.436069

e95b00a36dac3a2055f1aba26eec341f12557fa3

665

md

Markdown

packages/Networking/flutter_downloader.md

Ahmad4041/Flutter-Resources

4f9d2cca4db3fe3a48d3b8d3b23c1821e61bed67

[ "CC0-1.0" ]

1,230

2019-02-25T01:56:37.000Z

2022-03-29T18:29:21.000Z

packages/Networking/flutter_downloader.md

Ahmad4041/Flutter-Resources

4f9d2cca4db3fe3a48d3b8d3b23c1821e61bed67

[ "CC0-1.0" ]

3

2019-02-25T12:58:55.000Z

2019-06-09T08:24:29.000Z

packages/Networking/flutter_downloader.md

Ahmad4041/Flutter-Resources

4f9d2cca4db3fe3a48d3b8d3b23c1821e61bed67

[ "CC0-1.0" ]

175

2019-02-25T03:53:56.000Z

2022-02-14T16:38:25.000Z

Flutter Downloader A plugin for creating and managing download tasks. Supports iOS and Android. This plugin is based on `WorkManager` in Android and `NSURLSessionDownloadTask` in iOS to run download task in background mode. ```dart final taskId = await FlutterDownloader.enqueue( url: 'your download link', savedDir: 'the path of directory where you want to save downloaded files', showNotification: true, // show download progress in status bar (for Android) openFileFromNotification: true, // click on notification to open downloaded file (for Android) ); FlutterDownloader.registerCallback((id, status, progress) { // code to update your UI }); ```

36.944444

127

0.768421

eng_Latn

0.879811

e95b43bc24039b104a1181a946f6ce655159e8fe

416

md

Markdown

CodeNarc/UnnecessaryFinalOnPrivateMethod.md

Acidburn0zzz/docs-for-code-review-tools

9659492c76b988e14363dced6c2ab5f86fcdd6e0

[ "MIT" ]

1

2019-09-09T03:09:22.000Z

CodeNarc/UnnecessaryFinalOnPrivateMethod.md

Acidburn0zzz/docs-for-code-review-tools

9659492c76b988e14363dced6c2ab5f86fcdd6e0

[ "MIT" ]

null

CodeNarc/UnnecessaryFinalOnPrivateMethod.md

Acidburn0zzz/docs-for-code-review-tools

9659492c76b988e14363dced6c2ab5f86fcdd6e0

[ "MIT" ]

null

Pattern: Unnecessary `final` on private method Issue: - ## Description A private method is marked `final`. Private methods cannot be overridden, so marking it `final` is unnecessary. Example of violations: ``` groovy private final method() {} ``` ## Further Reading * [CodeNarc - UnnecessaryFinalOnPrivateMethod](http://codenarc.sourceforge.net/codenarc-rules-unnecessary.html#UnnecessaryFinalOnPrivateMethod)

24.470588

143

0.776442

eng_Latn

0.824671

e95b4e2b08000c124d57a4998b8b7c6f70d07db3

1,244

md

Markdown

docs-archive-a/2014/relational-databases/replication/mssql-repl-2147201021.md

v-alji/sql-docs-archive-pr.es-es

410a49b0a08c22fd4bc973078b563238d69c8b44

[ "CC-BY-4.0", "MIT" ]

1

2021-11-25T21:09:51.000Z

docs-archive-a/2014/relational-databases/replication/mssql-repl-2147201021.md

v-alji/sql-docs-archive-pr.es-es

410a49b0a08c22fd4bc973078b563238d69c8b44

[ "CC-BY-4.0", "MIT" ]

1

2021-11-25T02:22:05.000Z

2021-11-25T02:27:15.000Z

docs-archive-a/2014/relational-databases/replication/mssql-repl-2147201021.md

v-alji/sql-docs-archive-pr.es-es

410a49b0a08c22fd4bc973078b563238d69c8b44

[ "CC-BY-4.0", "MIT" ]

1

2021-09-29T08:53:04.000Z

--- title: MSSQL_REPL-2147201021 | Microsoft Docs ms.custom: '' ms.date: 06/13/2017 ms.prod: sql-server-2014 ms.reviewer: '' ms.technology: replication ms.topic: conceptual helpviewer_keywords: - MSSQL_REPL-2147201021 error ms.assetid: e8390319-7bf0-494a-9941-d2e4aad410ae author: MashaMSFT ms.author: mathoma ms.openlocfilehash: 4c8a4c517dc66223f5c98dd7b18cb2d338d5ca23 ms.sourcegitcommit: ad4d92dce894592a259721a1571b1d8736abacdb ms.translationtype: MT ms.contentlocale: es-ES ms.lasthandoff: 08/04/2020 ms.locfileid: "87670921" --- # <a name="mssql_repl-2147201021"></a>MSSQL_REPL-2147201021 ## <a name="message-details"></a>Detalles del mensaje ||| |-|-| |Nombre de producto|SQL Server| |Id. de evento|-2147201021| |Origen de eventos|MSSQLServer| |Nombre simbólico|| |Texto del mensaje|Publicación '%1' inactiva. Para activar esta publicación, inicie el Agente de instantáneas para generar la instantánea inicial.| ## <a name="explanation"></a>Explicación La publicación especificada está en estado inactivo. ## <a name="user-action"></a>Acción del usuario Para activar la publicación, ejecute el Agente de instantáneas de la publicación. ## <a name="internal-only"></a>Solo para uso interno

30.341463

149

0.751608

spa_Latn

0.522181

e95b78e0aef528f22436ac9606995dfb6bd15f44

411

md

Markdown

docs/about_greetings.md

Lindmeier/psconfeu-2018-workshop

4665eb3419b34a6317aef96ec4ffd6511962f063

[ "MIT" ]

null

docs/about_greetings.md

Lindmeier/psconfeu-2018-workshop

4665eb3419b34a6317aef96ec4ffd6511962f063

[ "MIT" ]

null

docs/about_greetings.md

Lindmeier/psconfeu-2018-workshop

4665eb3419b34a6317aef96ec4ffd6511962f063

[ "MIT" ]

null

# greetings ## about_greetings ``` ABOUT TOPIC NOTE: This module is greeting people ``` # SHORT DESCRIPTION This module is greeting people ``` ABOUT TOPIC NOTE: ``` # LONG DESCRIPTION This module is greeting people This module is greeting people This module is greeting people This module is greeting people ## Different greetings in different languages. You can also say hi.

15.222222

47

0.710462

eng_Latn

0.998814

e95c0f83b15266a88aaa6b9f373fd72e75dd7929

447

md

Markdown

_posts/2018-06-24-day133.md

BCara/bcara.github.io

c6faabea9a628af1af01b83cb5898e3418b80ed2

[ "BSD-3-Clause", "MIT" ]

null

_posts/2018-06-24-day133.md

BCara/bcara.github.io

c6faabea9a628af1af01b83cb5898e3418b80ed2

[ "BSD-3-Clause", "MIT" ]

null

_posts/2018-06-24-day133.md

BCara/bcara.github.io

c6faabea9a628af1af01b83cb5898e3418b80ed2

[ "BSD-3-Clause", "MIT" ]

null

--- layout: single title: "24th June 2018 - Medellin, Colombia" date: 2018-06-24 22:07:00 +0300 categories: daily author: true --- Colombia played Poland in the world cup today. We headed to a Plaza where it was filled with lively people. Colombia beat Poland and the whole place was ecstatic, the atmosphere was amazing. In the evening we hopped onto an overnight bus to Santa Marta and with all the excitement we quickly fell asleep.

26.294118

191

0.756152

eng_Latn

0.999737

e95c5df7d4f1c50edf4236285e2925865872ea97

10,110

md

Markdown

articles/virtual-network/virtual-network-manage-nsg-arm-portal.md

OpenLocalizationTestOrg/azure-docs-pr15_fr-FR

15e46e4307973230cd36bb4805c881d943cfb99b

[ "CC-BY-3.0", "CC-BY-4.0", "MIT" ]

null

articles/virtual-network/virtual-network-manage-nsg-arm-portal.md

OpenLocalizationTestOrg/azure-docs-pr15_fr-FR

15e46e4307973230cd36bb4805c881d943cfb99b

[ "CC-BY-3.0", "CC-BY-4.0", "MIT" ]

null

articles/virtual-network/virtual-network-manage-nsg-arm-portal.md

OpenLocalizationTestOrg/azure-docs-pr15_fr-FR

15e46e4307973230cd36bb4805c881d943cfb99b

[ "CC-BY-3.0", "CC-BY-4.0", "MIT" ]

null

<properties pageTitle="Gérer les NSGs à l’aide du portail de visualisation dans le Gestionnaire de ressources | Microsoft Azure" description="Découvrez comment gérer existant NSGs à l’aide du portail de visualisation dans le Gestionnaire de ressources" services="virtual-network" documentationCenter="na" authors="jimdial" manager="carmonm" editor="" tags="azure-resource-manager" /> <tags ms.service="virtual-network" ms.devlang="na" ms.topic="article" ms.tgt_pltfrm="na" ms.workload="infrastructure-services" ms.date="03/14/2016" ms.author="jdial" /> # <a name="manage-nsgs-using-the-preview-portal"></a>Gérer les NSGs à l’aide du portail preview > [AZURE.SELECTOR] - [Portail](virtual-network-manage-nsg-arm-portal.md) - [PowerShell](virtual-network-manage-nsg-arm-ps.md) - [Azure infrastructure du langage commun](virtual-network-manage-nsg-arm-cli.md) [AZURE.INCLUDE [virtual-network-manage-nsg-intro-include.md](../../includes/virtual-network-manage-nsg-intro-include.md)] [AZURE.INCLUDE [azure-arm-classic-important-include](../../includes/learn-about-deployment-models-rm-include.md)]modèle de déploiement classique. [AZURE.INCLUDE [virtual-network-manage-nsg-arm-scenario-include.md](../../includes/virtual-network-manage-nsg-arm-scenario-include.md)] ## <a name="retrieve-information"></a>Récupérer des informations Vous pouvez afficher votre NSGs existants, récupérer des règles pour un NSG existante et déterminer quelles ressources un NSG est associé à. ### <a name="view-existing-nsgs"></a>Affichage existants NSGs Pour afficher toutes les NSGs existants dans un abonnement, suivez les étapes ci-dessous. 1. Dans un navigateur, accédez à http://portal.azure.com et, si nécessaire, connectez-vous avec votre compte Azure. 2. Cliquez sur **Parcourir >** > **groupes de sécurité réseau**. ![Portail Azure - NSGs](./media/virtual-network-manage-nsg-arm-portal/figure1.png) 3. Consultez la liste des NSGs dans la carte de **groupes de sécurité réseau** . ![Portail Azure - NSGs](./media/virtual-network-manage-nsg-arm-portal/figure2.png) Pour afficher la liste des NSGs dans le groupe de ressources **Routage NSG** , suivez les étapes ci-dessous. 1. Cliquez sur **groupes de ressources >** > **Routage NSG** > **...**. ![Portail Azure - NSGs](./media/virtual-network-manage-nsg-arm-portal/figure3.png) 2. Dans la liste des ressources, recherchez les éléments affichant l’icône NSG, comme indiqué dans la carte de **ressources** ci-dessous. ![Portail Azure - NSGs](./media/virtual-network-manage-nsg-arm-portal/figure4.png) ### <a name="list-all-rules-for-an-nsg"></a>Liste de toutes les règles pour un NSG Pour afficher les règles d’un NSG nommés **NSG FrontEnd**, suivez les étapes ci-dessous. 1. Dans la carte de **groupes de sécurité réseau** , ou la carte de **ressources** ci-dessus, cliquez sur **NSG FrontEnd**. 2. Dans l’onglet **paramètres** , cliquez sur **règles de sécurité entrante**. ![Portail Azure - NSGs](./media/virtual-network-manage-nsg-arm-portal/figure5.png) 3. La carte de **sécurité règles de trafic entrant** s’affiche comme illustré ci-dessous. ![Portail Azure - NSGs](./media/virtual-network-manage-nsg-arm-portal/figure6.png) 4. Dans l’onglet **paramètres** , cliquez sur **règles de sécurité sortante** pour afficher les règles de trafic sortant. >[AZURE.NOTE] Pour afficher les règles par défaut, cliquez sur l’icône de **règles par défaut** en haut de la cuillère qui affiche les règles. ### <a name="view-nsgs-associations"></a>Afficher les associations NSGs Pour afficher ce que ressources qu'est la NSG **NSG FrontEnd** associer à, suivez les étapes ci-dessous. 1. Dans la carte de **groupes de sécurité réseau** , ou la carte de **ressources** ci-dessus, cliquez sur **NSG FrontEnd**. 2. Dans l’onglet **paramètres** , cliquez sur **sous-réseaux** pour afficher les sous-réseaux sont associés à la NSG. ![Portail Azure - NSGs](./media/virtual-network-manage-nsg-arm-portal/figure7.png) 3. Dans l’onglet **paramètres** , cliquez sur **interfaces réseau** pour afficher les cartes réseau est associés à la NSG. ## <a name="manage-rules"></a>Gérer les règles Vous pouvez ajouter des règles à un NSG existant, modifier les règles existantes et supprimer des règles. ### <a name="add-a-rule"></a>Ajouter une règle Pour ajouter une règle autorisant le trafic **entrant** pour le port **443** à partir de n’importe quel ordinateur à **NSG FrontEnd** NSG, suivez les étapes ci-dessous. 1. Dans la carte de **groupes de sécurité réseau** , ou la carte de **ressources** ci-dessus, cliquez sur **NSG FrontEnd**. 2. Dans l’onglet **paramètres** , cliquez sur **règles de sécurité entrante**. 3. Dans la carte de **sécurité règles de trafic entrant** , cliquez sur **Ajouter**. Puis, dans la carte de **Ajouter une règle sécurité entrante** , remplir les valeurs comme indiqué ci-dessous, puis cliquez sur **OK**. ![Portail Azure - NSGs](./media/virtual-network-manage-nsg-arm-portal/figure8.png) 4. Après quelques secondes, notez la nouvelle règle dans la carte de **règles de sécurité entrante** . ![Portail Azure - NSGs](./media/virtual-network-manage-nsg-arm-portal/figure9.png) ### <a name="change-a-rule"></a>Modifier une règle Pour modifier la règle créée ci-dessus pour autoriser le trafic entrant à partir d' **Internet** uniquement, suivez les étapes ci-dessous. 1. Dans la carte de **groupes de sécurité réseau** , ou la carte de **ressources** ci-dessus, cliquez sur **NSG FrontEnd**. 2. Dans l’onglet **paramètres** , cliquez sur la règle créée ci-dessus. 3. Dans la carte **https autoriser** , modifier la propriété **Source** comme indiqué ci-dessous, puis cliquez sur **Enregistrer**. ![Portail Azure - NSGs](./media/virtual-network-manage-nsg-arm-portal/figure10.png) ### <a name="delete-a-rule"></a>Supprimer une règle Pour supprimer la règle créée ci-dessus, suivez les étapes ci-dessous. 1. Dans la carte de **groupes de sécurité réseau** , ou la carte de **ressources** ci-dessus, cliquez sur **NSG FrontEnd**. 2. Dans l’onglet **paramètres** , cliquez sur la règle créée ci-dessus. 3. Dans la carte **https autoriser** , cliquez sur **Supprimer**, puis cliquez sur **Oui**. ![Portail Azure - NSGs](./media/virtual-network-manage-nsg-arm-portal/figure11.png) ## <a name="manage-associations"></a>Gérer les associations Vous pouvez associer un NSG à sous-réseaux et cartes réseau. Vous pouvez également dissocier un NSG à partir de n’importe quelle ressource qu'il est associée. ### <a name="associate-an-nsg-to-a-nic"></a>Associer un NSG à une carte réseau Pour associer **NSG FrontEnd** NSG à la **TestNICWeb1** carte réseau, suivez les étapes ci-dessous. 1. Dans la carte de **groupes de sécurité réseau** , ou la carte de **ressources** ci-dessus, cliquez sur **NSG FrontEnd**. 2. Dans l’onglet **paramètres** , cliquez sur **interfaces réseau** > **associer** > **TestNICWeb1**. ![Portail Azure - NSGs](./media/virtual-network-manage-nsg-arm-portal/figure12.png) ### <a name="dissociate-an-nsg-from-a-nic"></a>Dissocier une NSG à partir d’une carte réseau Pour dissocier **NSG FrontEnd** NSG à partir de la carte réseau **TestNICWeb1** , suivez les étapes ci-dessous. 1. À partir du portail Azure, cliquez sur **groupes de ressources >** > **Routage NSG** > **...** > **TestNICWeb1**. 2. Dans la carte **TestNICWeb1** , cliquez sur **sécurité modifier...** > **None**. ![Portail Azure - NSGs](./media/virtual-network-manage-nsg-arm-portal/figure13.png) >[AZURE.NOTE] Vous pouvez également utiliser cette carte pour associer la carte réseau à n’importe quel NSG existant. ### <a name="dissociate-an-nsg-from-a-subnet"></a>Dissocier une NSG à partir d’un sous-réseau Pour dissocier **NSG FrontEnd** NSG à partir du sous-réseau **FrontEnd** , suivez les étapes ci-dessous. 1. À partir du portail Azure, cliquez sur **groupes de ressources >** > **Routage NSG** > **...** > **TestVNet**. 2. Dans la carte de **paramètres** , cliquez sur **sous-réseaux** > **FrontEnd** > **groupe de sécurité réseau** > **Aucun**. ![Portail Azure - NSGs](./media/virtual-network-manage-nsg-arm-portal/figure14.png) 3. Dans la carte **FrontEnd** , cliquez sur **Enregistrer**. ![Portail Azure - NSGs](./media/virtual-network-manage-nsg-arm-portal/figure15.png) ### <a name="associate-an-nsg-to-a-subnet"></a>Associer un NSG à un sous-réseau Pour associer **NSG FrontEnd** NSG au sous-réseau **FronEnd** à nouveau, suivez les étapes ci-dessous. 1. À partir du portail Azure, cliquez sur **groupes de ressources >** > **Routage NSG** > **...** > **TestVNet**. 2. Dans la carte de **paramètres** , cliquez sur **sous-réseaux** > **FrontEnd** > **groupe de sécurité réseau** > **NSG FrontEnd**. 3. Dans la carte **FrontEnd** , cliquez sur **Enregistrer**. >[AZURE.NOTE] Vous pouvez également associer un NSG à un sous-réseau à partir de la carte de **paramètres** de thh NSG. ## <a name="delete-an-nsg"></a>Supprimer un NSG Vous pouvez uniquement supprimer une NSG si elle n’a pas associé à une ressource. Pour supprimer un NSG, suivez les étapes ci-dessous. 1. À partir du portail Azure, cliquez sur **groupes de ressources >** > **Routage NSG** > **...** > **NSG FrontEnd**. 2. Dans la carte de **paramètres** , cliquez sur **interfaces réseau**. 3. S’il existe les cartes réseau répertoriées, cliquez sur la carte réseau et suivez l’étape 2 de [Dissociate un NSG à partir d’une carte réseau](#Dissociate-an-NSG-from-a-NIC). 4. Répétez l’étape 3 pour chaque carte réseau. 5. Dans la carte de **paramètres** , cliquez sur **sous-réseaux**. 6. S’il existe une sous-réseaux répertoriés, cliquez sur le sous-réseau et suivez les étapes 2 et 3 dans [Dissociate un NSG à partir d’un sous-réseau](#Dissociate-an-NSG-from-a-subnet). 7. Faire défiler vers la gauche pour la carte **NSG FrontEnd** , puis cliquez sur **Supprimer** > **Oui**. [Portail Azure - NSGs](./media/virtual-network-manage-nsg-arm-portal/figure16.png) ## <a name="next-steps"></a>Étapes suivantes - [Activer la journalisation](virtual-network-nsg-manage-log.md) pour NSGs.

53.492063

220

0.725519

fra_Latn

0.928904

e95cdc029255b1221e458bcde34799d83444e4cf

10

md

Markdown

README.md

manthanhd/aws-poc

77dbde16b14be8f9cd8e14e1aa352390a66fb9c2

[ "MIT" ]

null

README.md

manthanhd/aws-poc

77dbde16b14be8f9cd8e14e1aa352390a66fb9c2

[ "MIT" ]

null

README.md

manthanhd/aws-poc

77dbde16b14be8f9cd8e14e1aa352390a66fb9c2

[ "MIT" ]

null

# aws-poc

5

9

0.6

pol_Latn

0.588883

e95e223240f4a3a5826a47a6cae2636d272bb2b7

401

md

Markdown

src/content/posts/2018-11-29-communication-with-metaphor.md

TomerAberbach/jillmarbach.com

ae7d733d6917d31882e1e0f6c0d59724309e7348

[ "MIT" ]

1

2020-04-28T12:31:57.000Z

src/content/posts/2018-11-29-communication-with-metaphor.md

TomerAberbach/jillmarbach.com

ae7d733d6917d31882e1e0f6c0d59724309e7348

[ "MIT" ]

null

src/content/posts/2018-11-29-communication-with-metaphor.md

TomerAberbach/jillmarbach.com

ae7d733d6917d31882e1e0f6c0d59724309e7348

[ "MIT" ]

null

--- title: Communication with Metaphor date: 2018-11-29T03:14:00.000Z tags: - TCNJ project - Illustrator - Design Fundamentals - project - graphic design --- ![Hair like a lion's mane project](/assets/metaphor-project.png "Hair like a lion's mane project") This project was created to convey the metaphor "Hair like a lion's mane." *Made with Illustrator for Design Fundamentals (AAV 251)*

26.733333

98

0.735661

eng_Latn

0.949703

e95eaa0f84122f52c12e759ba53214cfd354fe63

4,205

md

Markdown

published/201701/20161201 Using the NTP time synchronization.md

QiaoN/TranslateProject

191253c815756f842a783dd6f24d4dc082c225eb

[ "Apache-2.0" ]

1,994

2015-01-04T11:40:04.000Z

2022-03-29T17:18:18.000Z

published/201701/20161201 Using the NTP time synchronization.md

QiaoN/TranslateProject

191253c815756f842a783dd6f24d4dc082c225eb

[ "Apache-2.0" ]

1,257

2015-01-03T12:52:51.000Z

2022-03-31T12:52:12.000Z

published/201701/20161201 Using the NTP time synchronization.md

CN-QUAN/TranslateProject

89f982acd224c24de4431ce147aa1dedaa70b206

[ "Apache-2.0" ]

2,359

2015-01-04T02:09:02.000Z

2022-03-31T05:31:18.000Z

在 Ubuntu 中使用 NTP 进行时间同步 ========== NTP 是通过网络来同步时间的一种 TCP/IP 协议。通常客户端向服务器请求当前的时间，并根据结果来设置其时钟。这个描述是挺简单的，实现这一功能却是极为复杂的 - 首先要有多层 NTP 服务器，第一层 NTP 服务器连接原子时钟，第二层、第三层服务器则担起负载均衡的责任，以处理因特网传来的所有请求。另外，客户端可能也超乎你想象的复杂 - 它必须排除通讯延迟，调整时间的同时不干扰其它在服务器中运行的进程。幸运的是，所有的这些复杂性都进行了封装，你是不可见也不需要见到的。在 Ubuntu 中，是使用 `ntpdate` 和 `ntpd` 来同步时间的。 * [timedatectl](#timedatectl) * [timesyncd](#timesyncd) * [ntpdate](#ntpdate) * [timeservers](#timeservers) * [ntpd](#ntpd) * [安装](#installation) * [配置](#configuration) * [View status](#status) * [PPS Support](#Support) * [参考资料](#reference) ### <span id="timedatectl">timedatectl</span> 在最新的 Ubuntu 版本中，`timedatectl` 替代了老旧的 `ntpdate`。默认情况下，`timedatectl` 在系统启动的时候会立刻同步时间，并在稍后网络连接激活后通过 socket 再次检查一次。如果已安装了 `ntpdate` / `ntp`，`timedatectl` 会退而让你使用之前的设置。这样确保了两个时间同步服务不会相互冲突，同时在你升级的时候还保留原本的行为和配置。但这也意味着从旧版本的发行版升级时 `ntp`/`ntpdate` 仍会安装，因此会导致新的基于 systemd 的时间服务被禁用。 ### <span id="timesyncd">timesyncd</span> 在最新的 Ubuntu 版本中，`timesyncd` 替代了 `ntpd` 的客户端的部分。默认情况下 `timesyncd` 会定期检测并同步时间。它还会在本地存储更新的时间，以便在系统重启时做时间单步调整。通过 `timedatectl` 和 `timesyncd` 设置的当前时间状态和时间配置，可以使用 `timedatectl status` 命令来进行确认。 ``` timedatectl status Local time: Fri 2016-04-29 06:32:57 UTC Universal time: Fri 2016-04-29 06:32:57 UTC RTC time: Fri 2016-04-29 07:44:02 Time zone: Etc/UTC (UTC, +0000) Network time on: yes NTP synchronized: no RTC in local TZ: no ``` 如果安装了 NTP，并用它替代 `timedatectl` 来同步时间，则 `NTP synchronized` 将被设置为 `yes`。 `timedatectl` 和 `timesyncd` 用来获取时间的 nameserver 可以通过 `/etc/systemd/timesyncd.conf` 来指定，另外在 `/etc/systemd/timesyncd.conf.d/` 下还有灵活的附加配置文件。 ### <span id="ntpdate">ntpdate</span> 由于 `timedatectl` 的存在，各发行版已经弃用了 `ntpdate`，默认不再进行安装。如果你安装了，它会在系统启动的时候根据 Ubuntu 的 NTP 服务器来设置你电脑的时间。之后每当一个新的网络接口启动时，它就会重新尝试同步时间 —— 在这期间只要其涵盖的时间差不是太大，它就会慢慢偏移时间。该行为可以通过 `-B`/`-b` 开关来进行控制。 ``` ntpdate ntp.ubuntu.com ``` ### <span id="timeservers">时间服务器</span> 默认情况下，基于 systemd 的工具都是从 `ntp.ubuntu.com` 请求时间同步的。经典的基于 `ntpd` 的服务基本上都是使用 `[0-3].ubuntu.pool.ntp.org` 池中的 `2.ubuntu.pool.ntp.org`，还有 `ntp.ubuntu.com`，此外需要的话还支持 IPv6。如果想强制使用 IPv6，可以使用 `ipv6.ntp.ubuntu.com`，不过这并非默认配置。 ### <span id="ntpd">ntpd</span> ntp 的守护进程 `ntpd` 会计算你的系统时钟的时间偏移量并且持续的进行调整，所以不会出现时间差距较大的更正，比如说，不会导致不连续的日志。该进程只花费少量的进程资源和内存，但对于现代的服务器来说实在是微不足道的了。 ### <span id="installation">安装</span> 要安装 `ntpd`，在终端命令行中输入： ``` sudo apt install ntp ``` ### <span id="configuration">配置</span> 编辑 `/etc/ntp.conf` —— 增加/移除 `server` 行。默认配置有以下服务器： ``` # Use servers from the NTP Pool Project. Approved by Ubuntu Technical Board # on 2011-02-08 (LP: #104525). See http://www.pool.ntp.org/join.html for # more information. server 0.ubuntu.pool.ntp.org server 1.ubuntu.pool.ntp.org server 2.ubuntu.pool.ntp.org server 3.ubuntu.pool.ntp.org ``` 修改配置文件之后，你需要重新加载 `ntpd`： ``` sudo systemctl reload ntp.service ``` ### <span id="status">查看状态</span> 使用 `ntpq` 来查看更多信息： ``` # sudo ntpq -p remote refid st t when poll reach delay offset jitter ============================================================================== +stratum2-2.NTP. 129.70.130.70 2 u 5 64 377 68.461 -44.274 110.334 +ntp2.m-online.n 212.18.1.106 2 u 5 64 377 54.629 -27.318 78.882 *145.253.66.170 .DCFa. 1 u 10 64 377 83.607 -30.159 68.343 +stratum2-3.NTP. 129.70.130.70 2 u 5 64 357 68.795 -68.168 104.612 +europium.canoni 193.79.237.14 2 u 63 64 337 81.534 -67.968 92.792 ``` ### <span id="Support">PPS 支持</span> 从 Ubuntu 16.04 开始，ntp 支持 PPS 规范，给 ntp 提供了本地时间源，以提供更高的精度。查看下边列出的链接来获取更多配置信息。 ### <span id="reference">参考资料</span> * 参考 [Ubuntu Time][1] wiki 页来获取更多信息 * [ntp.org，网络时间协议项目主页][2] * [ntp.org，关于配置 PPS 的 FAQ][3] -------------------------------------------------------------------------------- via: https://help.ubuntu.com/lts/serverguide/NTP.html 作者：[Ubuntu][a] 译者：[GHLandy](https://github.com/GHLandy) 校对：[jasminepeng](https://github.com/jasminepeng) 本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出 [a]:https://help.ubuntu.com/lts/serverguide/NTP.html [1]:https://help.ubuntu.com/community/UbuntuTime [2]:http://www.ntp.org/ [3]:http://www.ntp.org/ntpfaq/NTP-s-config-adv.htm#S-CONFIG-ADV-PPS

31.380597

214

0.68157

yue_Hant

0.663751

e95f434001282acb8e1b13e0175d941a4b0b74e6

8,745

md

Markdown

devplatform/helion/user/services/1.0port-service.html.md

hphelion/documentation.md

aa334b053001ba82883875f63725e69a54fd35e5

[ "Apache-2.0" ]

null

devplatform/helion/user/services/1.0port-service.html.md

hphelion/documentation.md

aa334b053001ba82883875f63725e69a54fd35e5

[ "Apache-2.0" ]

null

devplatform/helion/user/services/1.0port-service.html.md

hphelion/documentation.md

aa334b053001ba82883875f63725e69a54fd35e5

[ "Apache-2.0" ]

null

--- layout: 1.0default-devplatform permalink: /als/v1/user/services/port-service/ product: devplatform1.0 title: "HP Helion 1.0 Development Platform: Port Service (Harbor) " product-version1: HP Helion Development Platform product-version2: HP Helion Development Platform 1.1 role1: Application Developer role2: ISV Developer role3: Service Developer role4: Systems Administrator authors: Jayme P ---  # HP Helion 1.0 Development Platform: Port Service (Harbor) {#port-service-harbor} [See the Helion 1.1 Development Platform version of this page](/helion/devplatform/1.1/als/user/services/port-service/) HTTP and HTTPS ports and routing are provided automatically for all web applications deployed to Application Lifecycle Service (unless [processes: web:](/als/v1/user/deploy/manifestyml/#web) is set to "\~"). If your application requires additional TCP or UDP ports, use the Harbor service to allocate them. ##Requesting a Port {#requesting-a-port} Additional ports are provisioned like any other data service. To request a port with the Helion command-line client: helion create-service harbor debug-port To request a port from Harbor in the **manifest.yml** file, add it in the [**services**](/als/v1/user/deploy/manifestyml/#services) block. For example: name: port-test mem: 256 services: my-port: harbor This creates a TCP port tunnel which the application can access on the host and port specified in the \$HELION\_SERVICES environment variable. The example above might create the following "my-port" object in \$HELION\_SERVICES: { "my-port": { "hostname": "192.168.68.111", "host": "192.168.68.111", "port": 30134, "name": "cf7f868a-8b7b-4ac8-ab4d-9fd87efb7c09", "node_id": "harbor_node_1", "int_port": 4100, "ext_hostname": "ports.example.com", "ext_host": "15.185.104.122" } } This provides the following information: - **hostname**: The internal hostname (if configured) of the node providing the service (i.e. the Harbor node). If none is configured by the admin, this will show the internal IP address. - **host**: The internal IP address of the Harbor node. - **port**: The external port number exposed by the service. Connections from external clients and other internal applications (those not directly bound to the service) will connect with this port number. - **name**: The service instance ID (Application Lifecycle Service internal refer). - **node\_id**: The Harbor node ID (Application Lifecycle Service internal). - **int\_port**: The port on the application container which forwards to Harbor (see also [Harbor Environment Variables](#port-service-env-vars)). Application(s) bound to the service should connect to this port. Access to the port from outside of the Application Lifecycle Service system/cluster may or may not be exposed, depending on how the Harbor service is configured by the Admin. If Harbor is set up to allow public port access, the following two settings will also be shown: - **ext\_hostname**: The public hostname (if configured) exposing the port. - **ext\_host**: The public IP address exposing the port. **Note** To remotely check the settings and credentials of any Application Lifecycle Service service, use the [**helion service**](/als/v1/user/reference/client-ref/#command-services) command. ### Harbor Environment Variables[](#harbor-environment-variables "Permalink to this headline") If there is only one Harbor service, the **HELION_HARBOR** environment variable can be used to get the internal port number. If there is more than one Harbor service, **HELION_HARBOR** is not available. Instead, a custom **HELION\_HARBOR\_<SERVICE\_NAME>** environment variable will be created for each harbor service (service name upper-cased with hyphens replaced by underscores). For example, if your *manifest.yml* file configures the following services: services: udp-port: harbor tcp-port: harbor Two environment variables would be created: `HELION_HARBOR_UDP_PORT` and `HELION_HARBOR_TCP_PORT`. This naming scheme can be used in conjunction with the **HELION\_APP\_NAME\_UPCASE** environment variable. For example, in an app with the following harbor services defined: services: udp-${name}: harbor tcp-${name}: harbor The Harbor port number for the UDP service could be accessed within the container with a construct such as: UDP_SERVICE_NAME=HELION_HARBOR_UDP_${HELION_APP_NAME_UPCASE} UDP_SERVICE_PORT=${!UDP_SERVICE_NAME} **Note** To use declarations like these in [*hooks*](/als/v1/user/deploy/manifestyml/#hooks), put them in a separate bash script. Brace expansion and grouping cannot be used directly in YAML files. ##Setting the Port Protocols {#setting-the-port-protocols} Harbor supports both the TCP and UDP protocols. When you provision a service with Harbor it will create a TCP enabled port by default. If you want to have a UDP port provisioned instead, you simply prefix your service name with udp, for example: helion create-service harbor udp-debug-port If you have an application that requires both TCP **and** UDP, you can prefix your service name with either *multi-* or *both-* . For example: helion create-service harbor both-debug-port Harbor will then create UDP and TCP proxies for your application so that applications like DNS can use both protocols on the same provisioned port. ##Multiple Application Instances {#multiple-application-instances} Harbor recognizes when you have multiple instances of your app running and will update the available app backends accordingly. - For TCP connections it will round-robin between your available backends on each new connection, in a similar fashion to the router component. - For UDP this is not the case, as it is a stateless protocol. For multiple UDP backends harbor will use a FIFO queue, that is the first app instance available becomes the primary backend, and any added later are queued. HTTPS via Harbor[](#https-via-harbor "Permalink to this headline") ------------------------------------------------------------------- SSL termination of HTTPS to applications hosted on Application Lifecycle Service normally happens at the Router. There is currently no mechanism for users to add SSL certificates for their own applications to the Router, but you can expose an external HTTPS interface via the Harbor port service which uses your SSL certificates. To do this, upload the SSL certificate(s) and key(s) along with your application, and expose your application server directly on the TCP port provided by Harbor. For example, an application running through the port service might have a URL such as: *https://harbor-node.helion.com:35048/* You can set up aliases to this URL using DNS, but the explicit port specification must always be added. **Notes:** - When using this approach, the hostname / IP address of the app will be the one provided by the Harbor node the client will connect using the Harbor-assigned port number, **not** 443. - Using Harbor in this way does **not** take advantage of any load balancing set up for regular web traffic through the Routers and Load Balancer. - If you have multiple instances of your app routing through a Harbor TCP port, connections will be distributed via round-robin. ### HTTPS Container Proxy[](#https-container-proxy "Permalink to this headline") If you are using a framework such as Python or Perl which sets up uWSGI (or any other framework that provides its own intermediate web server) Harbor can provision an HTTPS server in the app container that forwards HTTPS requests to the framework's HTTP server. To do this, add the suffix **https** to the name of your Harbor service. For example: name: harbor-test-app services: custom-cert-https: harbor Put your server certificate and key (named *harbor.crt* and *harbor.key* respectively) in a folder called *certs* in the application's root directory. For example: app_root certs harbor.crt harbor.key ... Alternatively, use a standalone or buildpack setup which provisions its own intermediate web server instead. ### Multiple SSL Certificates[](#multiple-ssl-certificates "Permalink to this headline") If your application uses multiple SSL certificates, use the following naming scheme: - *harbor service name*.key - *harbor service name*.crt For example: app_root certs harbor-https-custom-1.crt harbor-https-custom-2.key ... The proxy will look for these certs before reverting to `harbor.crt` and `harbor.key`.

38.69469

216

0.746484

eng_Latn

0.994567

e9601b1194569d6bb036afef7909215082193ab0

1,334

md

Markdown

CHANGELOG.md

Sieg/RegExDependency

23ff72bc8846af0d4c08c43cc741b8156cae4158

[ "MIT" ]

1

2017-08-02T14:59:47.000Z

CHANGELOG.md

Sieg/RegExDependency

23ff72bc8846af0d4c08c43cc741b8156cae4158

[ "MIT" ]

1

2021-03-28T21:09:08.000Z

2021-03-28T21:09:14.000Z

CHANGELOG.md

Sieg/RegExDependency

23ff72bc8846af0d4c08c43cc741b8156cae4158

[ "MIT" ]

null

# Change Log for Regex Dependency component All notable changes to this project will be documented in this file. The format is based on [Keep a Changelog](http://keepachangelog.com/) and this project adheres to [Semantic Versioning](http://semver.org/). ## [v1.0.0] - Unreleased ### Added - Code quality tools: sonarcloud, phpcs, phpstan - Collection class for loading and combinined multiple configurations - Support different regex openings/closings ### Changed - ConfigurationItemCollection interface object required by Container constructor, no simple array anymore - Repository transferred to FreshAdvance organization - Vendor name changed to fresh-advance - Namespace changed to FreshAdvence - Travis is not used anymore. Github actions is used as ci ### Fixed - Fix problematic slash cases - Improve performance by removing tests of expression on runtime ### Removed - Container::getConfiguration - As configuration is now applied on container, and updates container state, there is no way (and actually no point) to get reusable configuration in a simple way anymore. ## [v0.3.0] - 2019-11-10 ### Added - Make component compliant to PSR-11 [v1.0.0]: https://github.com/FreshAdvance/regex-dependency/compare/v0.3.0...master [v0.3.0]: https://github.com/FreshAdvance/regex-dependency/compare/b607c1091...v0.3.0

37.055556

175

0.772114

eng_Latn

0.970027

e96023c2edc917d723e1f5bcb4a008646ac026a8

447

md

Markdown

admin/standups/2021-06-01.md

cse110-sp21-group23/cse110-sp21-group23

c9d540c8b5e5f4b2f90a73776ec654b63b03f09a

[ "MIT" ]

1

2021-06-15T21:36:40.000Z

admin/standups/2021-06-01.md

cse110-sp21-group23/cse110-sp21-group23

c9d540c8b5e5f4b2f90a73776ec654b63b03f09a

[ "MIT" ]

52

2021-06-07T18:51:16.000Z

2021-06-13T22:08:52.000Z

admin/standups/2021-06-01.md

cse110-sp21-group23/cse110-sp21-group23

c9d540c8b5e5f4b2f90a73776ec654b63b03f09a

[ "MIT" ]

null

# 2021-06-01 Standup ### **Bas Beeuwsaert:** ### **Caroline Xiong:** ### **Christopher Yoon:** - Fixed some bugs regarding drag and drop in the frontend / backend. - Will work on getting drag and drop to work across lists in the weekly view ### **Daniel Huynh:** - Was able to create a Navbar for the top and pushed it! ### **Kent Utomo:** - fixed edit bullet ### **Michael Fu:** ### **Sophia Lui:** ### **Wen Tian:** ### **Yuchen Jin:**

19.434783

76

0.626398

eng_Latn

0.958647

e9607316c41ba0d6c984c03cebef0f73284d2ea5

107

md

Markdown

CHANGES.md

wilsonjie/ambrose

da7bcb932c418c157d9c372a4ca5f1884b874d78

[ "Apache-2.0" ]

355

2015-01-01T09:27:30.000Z

2021-09-14T18:47:46.000Z

CHANGES.md

wilsonjie/ambrose

da7bcb932c418c157d9c372a4ca5f1884b874d78

[ "Apache-2.0" ]

19

2015-01-07T18:20:38.000Z

2020-01-22T18:52:17.000Z

CHANGES.md

wilsonjie/ambrose

da7bcb932c418c157d9c372a4ca5f1884b874d78

[ "Apache-2.0" ]

113

2015-01-06T17:02:43.000Z

2021-06-02T17:09:41.000Z

# Ambrose Change Log ## Version 0.4.2 - #177 Updates default ScriptStatusServer port from 8080 to random

17.833333

66

0.757009

eng_Latn

0.361206

e960b440b195409bbc0941b1dce0f0bcb90c80cb

244

md

Markdown

data/2020/14-membuat-aplikasi-php-microservices-dengan-aws-cancelled.md

iamyuu/phpid-learning

ab8e0fde95be97008e2a827c5a2a3bcff9cf439f

[ "MIT" ]

125

2020-04-12T14:49:53.000Z

2021-01-21T00:10:00.000Z

data/2020/14-membuat-aplikasi-php-microservices-dengan-aws-cancelled.md

iamyuu/phpid-learning

ab8e0fde95be97008e2a827c5a2a3bcff9cf439f

[ "MIT" ]

9

2020-05-15T02:39:13.000Z

2021-01-26T10:55:30.000Z

data/2020/14-membuat-aplikasi-php-microservices-dengan-aws-cancelled.md

iamyuu/phpid-learning

ab8e0fde95be97008e2a827c5a2a3bcff9cf439f

[ "MIT" ]

36

2020-04-12T17:16:54.000Z

2021-01-25T00:24:23.000Z

### Membuat Aplikasi PHP Microservices dengan AWS (cancelled) - Waktu: Senin, 29 Juni 2020 - Pukul: 19:00 - Pemateri: Om Petra Novandi Barus - AWS - Slide: empty - Video: empty - Registrasi: empty - Sesi: 36 - Kategori: web, aws - Deskripsi: -

22.181818

61

0.704918

ind_Latn

0.517795

e961a4e56dcbeb62bac626bff89c4f482fb58d0c

73

md

Markdown

README.md

hebbel4/redux-book-website

9cee5fbb095135db9f42662ad11274c9cb518e4c

[ "MIT" ]

null

README.md

hebbel4/redux-book-website

9cee5fbb095135db9f42662ad11274c9cb518e4c

[ "MIT" ]

null

README.md

hebbel4/redux-book-website

9cee5fbb095135db9f42662ad11274c9cb518e4c

[ "MIT" ]

null

# redux-book-website Built a simple book website using redux and react.

18.25

50

0.780822

eng_Latn

0.929933

e96213a02e76a402f6525b2e6547b8fb9f9fbf82

56

md

Markdown

README.md

jwinarske/meta-juce

2eedb69c4de4bd50b827b50463b0a1c8647c152b

[ "MIT" ]

null

README.md

jwinarske/meta-juce

2eedb69c4de4bd50b827b50463b0a1c8647c152b

[ "MIT" ]

null

README.md

jwinarske/meta-juce

2eedb69c4de4bd50b827b50463b0a1c8647c152b

[ "MIT" ]

null

# meta-juce Yocto meta layer for the JUCE C++ framework

18.666667

43

0.75

eng_Latn

0.750199

e962d19bcdc01020c9f9c407257fc06791b906b7

4,228

md

Markdown

docs/antipatterns/index.md

OtacilioN/architecture-center.pt-br

ccefae434b398bb134edd3fb2f67f99fa0b055f2

[ "CC-BY-4.0", "MIT" ]

null

docs/antipatterns/index.md

OtacilioN/architecture-center.pt-br

ccefae434b398bb134edd3fb2f67f99fa0b055f2

[ "CC-BY-4.0", "MIT" ]

null

docs/antipatterns/index.md

OtacilioN/architecture-center.pt-br

ccefae434b398bb134edd3fb2f67f99fa0b055f2

[ "CC-BY-4.0", "MIT" ]

null

--- title: Antipadrões de desempenho para aplicativos em nuvem description: Práticas comuns que podem causar problemas de escalabilidade. author: dragon119 ms.date: 06/05/2017 ms.openlocfilehash: 423fe6533e57268610f625f523714cd1bce89546 ms.sourcegitcommit: b0482d49aab0526be386837702e7724c61232c60 ms.translationtype: HT ms.contentlocale: pt-BR ms.lasthandoff: 11/14/2017 ms.locfileid: "24538706" --- # <a name="performance-antipatterns-for-cloud-applications"></a>Antipadrões de desempenho para aplicativos em nuvem Um *antipadrão desempenho* é uma prática comum que pode causar problemas de escalabilidade quando um aplicativo está sob pressão. Aqui está um cenário comum: um aplicativo se comporta bem durante o teste de desempenho. Ele é liberado para produção e começa a lidar com cargas de trabalho reais. Nesse ponto, ele começa a executar mal —, rejeitando solicitações do usuário, atrasando ou lançando exceções. A equipe de desenvolvimento enfrenta duas perguntas: - Por que não esse comportamento é exibido durante o teste? - Como podemos corrigir isso? A resposta à primeira pergunta é simples. É muito difícil em um ambiente de teste para simular usuários reais, seus padrões de comportamento e os volumes de trabalho, que eles podem executar. A única maneira totalmente garantida de compreender como um sistema se comporta sob carga é observá-lo em produção. Para ser claro, estamos não sugerindo que você deve ignorar o teste de desempenho. Testes de desempenho são cruciais para a obtenção de métricas de desempenho de linha de base. Mas você deve estar preparado para observar e corrigir problemas de desempenho quando eles ocorrem no sistema de produção. A resposta à segunda pergunta, como corrigir o problema, é menos direto. Qualquer número de fatores pode contribuir e, às vezes, o problema só se manifesta em determinadas circunstâncias. Instrumentação e registro em log são fundamentais para localizar a causa raiz, mas você também precisa saber o que procurar. Com base em nossos contratos com clientes do Microsoft Azure, identificamos alguns dos problemas de desempenho mais comuns que os clientes veem em produção. Para cada antipadrão, descrevemos por que o antipadrão normalmente ocorre, sintomas de antipadrão e técnicas para resolver o problema. Nós também fornecemos o código de exemplo que ilustra o antipadrão e uma sugestão de solução. Esses antipadrões podem parecer óbvios quando você lê as descrições, mas eles ocorrem com mais frequência do que você imagina. Às vezes, um aplicativo herda um design que funcionou no local, mas não escala na nuvem. Ou um aplicativo pode iniciar com um design bem simples, mas à medida que novos recursos são adicionados, um ou mais desses antipadrões podem surgir. Independentemente, este guia ajudará você a identificar e corrigir esses antipadrões. Aqui está a lista das antipadrões que nós identificamos: | Antipadrão | Descrição | |-------------|-------------| | [Banco de Dados Ocupado][BusyDatabase] | Descarregando muito processamento para um armazenamento de dados. | | [Front-End Ocupado][BusyFrontEnd] | Movendo tarefas de uso intensivo de recursos em threads em segundo plano. | | [E/S com ruídos][ChattyIO] | Continuamente enviar várias solicitações de rede pequena. | | [Busca Incorreta][ExtraneousFetching] | Recuperando dados mais que o necessário, resultando em E/S desnecessária. | | [Instanciação Inadequada][ImproperInstantiation] | Repetidamente, criação e destruição de objetos que são projetados para serem compartilhados e reutilizados. | | [Persistência Monolítica][MonolithicPersistence] | Usando o mesmo armazenamento de dados para dados com padrões de uso muito diferentes. | | [Sem cache][NoCaching] | Falha ao armazenar dados em cache. | | [E/S Síncrona][SynchronousIO] | Bloquear o thread de chamada enquanto a E/S é concluída. | [BusyDatabase]: ./busy-database/index.md [BusyFrontEnd]: ./busy-front-end/index.md [ChattyIO]: ./chatty-io/index.md [ExtraneousFetching]: ./extraneous-fetching/index.md [ImproperInstantiation]: ./improper-instantiation/index.md [MonolithicPersistence]: ./monolithic-persistence/index.md [NoCaching]: ./no-caching/index.md [SynchronousIO]: ./synchronous-io/index.md

84.56

607

0.79825

por_Latn

0.999878

e963a90d3290dd9b8cdd1c19408bdff68720586f

65,047

md

Markdown

source/index.html.md

smaxtec/slate

4727875576b98872c43e16e4fd32428dba0162e6

[ "Apache-2.0" ]

null

source/index.html.md

smaxtec/slate

4727875576b98872c43e16e4fd32428dba0162e6

[ "Apache-2.0" ]

1

2020-03-30T06:56:25.000Z

source/index.html.md

smaxtec/slate

4727875576b98872c43e16e4fd32428dba0162e6

[ "Apache-2.0" ]

null

--- title: smaXtec Integration API Reference language_tabs: - bash - python toc_footers: - <a href='https://messenger-staging.smaxtec.com/'>smaXtec Messenger (staging)</a> - <a href='https://api-staging.smaxtec.com/integration/v2/'>smaXtec API (staging)</a> includes: - errors search: true --- # Introduction Welcome to the smaXtec Integration API! 🐮 You can use our API to access intern API endpoints, which can get information on animals and animal events in our database. The Integration API offer the following advantages: - The animals are identified with the eartag/EID and not the smaXtec internal IDs. - External partners do not need to choose to update or create. They can simply send the current state of all objects and smaXtec will do the synchronisation. ## Endpoints The *live* `[endpoint]` is `https://api.smaxtec.com/integration/v2` and the *staging* is `https://api-staging.smaxtec.com/integration/v2`. The *staging* endpoint can be used for **testing**. ## Parameters and Responses The parameters in the data of the PUT API calls and the response of the GET/PUT API calls are the same. This means that the output can be taken and provided to a PUT method. ## User Registration The registration is done via the [smaXtec messenger](https://messenger.smaxtec.com). If the user is registered over the [smaXtec staging messenger](https://messenger-staging.smaxtec.com) no registration e-mail is sent. You need to contact us so we can activate your user. ## Design Manual for Herd Management Systems Our goal is that smaXtec users have a cohesive experience when using our products. Having a consistent communication - both in design and text - is essential as it enables us to support customers the best way possible. If the same wording and color scheme for alerts and icons is used, our customer support team can help customers easier and faster when problems or questions arise when using smaXtec within a herd management system. We ask you to follow this guideline when implementing smaXtec in your system to ensure the best experience for our joint customers. Here you can find the [smaXtec design manual](../documents/20210706_Design_Manual_HMS_Integration.pdf). ## Common Tasks For all common tasks the [authentication](#authentication) is necessary. ### Get Organisation of User One user can have multiple organisations. With the logged in user the user can [get all organisations](#get-all-organisations). ### Add or Update an Animal For adding an animal to an organisation (`organisation_id`) at least the required fields in the animal data (link to animal parameters) need to be filled in. With the [PUT call](#create-update-single-animal) the animal can be added. For updating an animal the `organisation_id` and the `official_id` of the animal, which should be updated, need to be in the route. Write all changing parameters in the data and use the [animal PUT](#create-update-single-animal) method. The response of the animal calls can be put in as data to the animal put call. Changes are detected and are applied. ### Add heat, insemination, pregnancy result, dry off, calving confirmation, abort and diagnosis These occurrences are stored as [events](#events) where insemination, pregnancy result, calving confirmation and abort are the event types. To add an event the event type (`event_type`) and the event time (`event_ts`) need to be provided to the [event PUT method](#create-events). Regarding of the type additional information can be added which is listed in the parameter list. The chronological order of an animal life and how the events happen is the following: `-> heat -> insemination -> pregnancy_result -> dry_off -> calving_confirmation ->` or `-> heat -> insemination -> pregnancy_result -> abort ->` A `diagnosis` can be made and added at any time in the life of the cow. ## User-Agent The *user-agent* should be used so that we know which client is requesting or sending data to us. It should contain the name of your software and the version. e.g.: 'HerdManagerSoftwareXYZ/2.4' ## Datetime Fields which store the date and time are formatted in the ISO 8601 standard. For example `2016-10-01T14:00:00+00:00`. Some fields contain ms as well, but they can be ignored. ## Placeholder Several placeholders are used in this document. | Placeholder | Description | Example | | ----------------- | ---------------------------------------------------------------------------------------- | ----------------------------------------------- | | [token] | [Authentication](#authentication) token which can be get over the API | yx2zvuB8JD8ppwGti84OT8Muq5eiB2b2EZqsqC-HOXUvLSg | | [endpoint] | Endpoint to the integration API | https://api-staging.smaxtec.com/integration/v2 | | [email] | E-mail address from the registered user | user@smaxtec.com | | [password] | Password from the registered user | super_secret_password | | [organisation_id] | smaXtec intern ID of the organisation. Can be [get](#get-all-organisations) over the API | 123456qwertz | | [official_id] | The official id of the animal. This is in the most cases the eartag of the animal. | AT111111112 | | [device_id] | The id of a device. | 0600000001 | | [user_agent] | User - Agent | HerdManagerSoftwareXYZ/2.4 | | [language] | Language of the wanted translated text. | en | | [event_type] | [Event type](#get-all-events) of an animal event. | HEALTH_102 | # Authentication > Request ```python import requests email='user@smaxtec.com' password='super_secret_password' integration_name='my-integration-app-name' endpoint = 'https://api-staging.smaxtec.com/integration/v2' route = endpoint + '/users/session_token' user_agent = 'HerdManagerSoftwareXYZ/2.4' headers = {'accept': 'application/json', 'User-Agent': user_agent} data = { "user": email, "password": password, "integration_name": integration_name } r = requests.post(route, headers=headers, json=data) status_code = r.status_code authentication = r.json() ``` ```bash curl -X POST "[endpoint]/users/session_token?user=[email]&password=[password]" \ -H "accept: application/json" \ -H "User-Agent: [user_agent]" ``` > Response example ```json { "token": "yx2zvuB8JD8ppwGti84OT8Muq5eiB2b2EZqsqC-HOXUvLSg" } ``` An authorization token is requested over the API. The Response is a token which needs to be in all API requests to the server in a header that looks like the following: `-H "authorization: Bearer [token]"` For example: `-H "authorization: Bearer yx2zvuB8JD8ppwGti84OT8Muq5eiB2b2EZqsqC-HOXUvLSg"` The token expires after 24 hours. <aside class="notice">The authorization header is needed in all following calls.</aside> **HTTP Request** `POST "[endpoint]/users/session_token?user=[email]&password=[password]"` # Organisations ## Get All Organisations > Request ```python import requests endpoint = 'https://api-staging.smaxtec.com/integration/v2' route = endpoint + '/organisations' token = 'yx2zvuB8JD8ppwGti84OT8Muq5eiB2b2EZqsqC-HOXUvLSg' user_agent = 'HerdManagerSoftwareXYZ/2.4' headers = { 'accept': 'application/json', 'User-Agent': user_agent, 'Authorization': 'bearer ' + token } r = requests.get(route, headers=headers) status_code = r.status_code all_user_organisations = r.json() ``` ```bash curl -X GET "[endpoint]/organisations" \ -H "accept: application/json" \ -H "Authorization: bearer [token]" \ -H "User-Agent: [user_agent]" ``` > Response example ```json [ { "name": "Organisation Name", "organisation_id": "123456qwertz", "permissions": [ "read", "groups.update", "animals.create", "animals.update", "animals.archive", "animals.changetags", "animals.changegroup", "devices.update", "lactations.update", "diagnosis.update", "heats.update", "organisations.update", "annotations.update" ], "role": "admin", "timezone": "Europe/Vienna" } ] ``` This endpoint retrieves all organisations of the user. For the Integration API calls the `organisation_id` is needed to make changes to the animals of the organisation. **HTTP Request** `GET [endpoint]/organisations` **Response** | Parameter | Description | | --------------- | --------------------------------------------------- | | name | Name of the Organisation. | | organisation_id | ID of the organisation where the animal belongs to. | | permissions | Permission the user has for this organisation. | | role | Role the user has for this organisation. | | timezone | Timezone of the organisation. | ## Create An Organisation > Request ```python import requests endpoint = 'https://api-staging.smaxtec.com/integration/v2' route = endpoint + '/organisations' data = { "name": "Farm XY", "timezone": "Europe/Vienna", "account": { "name": "Farm XY", "vat_number": "ATU99999999", "address": { "line1": "Farmer Joe", "line2": "Streetname 25", "line3": "Block 4", "country_code": "AT", "region": "Steiermark", "city": "Graz", "postal_code": "8020", "address_type": "default" } } } token = 'yx2zvuB8JD8ppwGti84OT8Muq5eiB2b2EZqsqC-HOXUvLSg' user_agent = 'HerdManagerSoftwareXYZ/2.4' headers = { 'accept': 'application/json', 'User-Agent': user_agent, 'Authorization': 'bearer ' + token } r = requests.post(route, json=data, headers=headers) status_code = r.status_code organisation = r.json() ``` ```bash curl -X POST "[endpoint]/integration/v2/organisations" \ -H "accept: application/json" \ -H "Authorization: bearer [token]" \ -H "Content-Type: application/json" \ -H "User-Agent: [user_agent]" \ -d "{\"account\": {\"name\": \"Farm XY\", \"vat_number\": \"ATU99999999\", \"address\": {\"line1\": \"Farmer Joe\", \"line2\": \"Streetname 25\", \"line3\": \"Block 4\", \"country_code\": \"AT\", \"region\": \"Steiermark\", \"city\": \"Graz\", \"postal_code\": \"8020\", \"address_type\": \"default\" } }, \"name\": \"Farm XY\", \"timezone\": \"Europe/Vienna\"}" ``` > Response example ```json { "account_id": "5dasdfasdfasdf1234567890", "_id": "5dasdfasdfasdf1234567890", "devices": [], "timezone": "Europe/Vienna", "name": "Farm XY", "organisation_settings": { "algorithms": { "105_threshold": 0.5, "105_sigmoid_threshold": 0.3, "106_threshold": 0.75, "104_svm_sensitivity": "normal", "704_threshold": 50.0, "703_threshold": 60.0, "702_threshold": 50.0, "101_threshold": 2.0, "104_svm_threshold": 0.5, "104_threshold": 0.75, "estrus_algo": "HeatIndexStable50" } }, "metadata": {}, "features": [], "animal_groups": [], "created_by": "5aasdfasdfasdf1234567890" } ``` This endpoint creates an organisation and its billing address. The smaXtec intern organisation_id is returned as `_id`. **HTTP Request** `GET "[endpoint]/organisations"` **URL Parameters** | Parameter | Description | | | ------------ | --------------------------------------------- | ---------- | | name | Name of the farm | `required` | | timezone | Timezone of the farm | `required` | | **account** | | | | name | Name of the account | `required` | | vat_number | Value added tax identification number | | | **address** | | | | line1 | First line of the address | `required` | | line2 | Second line of the address | `required` | | line3 | Third line of the address | | | country_code | Country code | `required` | | region | Region | | | city | City | | | postal_code | Postal code / ZIP | | | address_type | Type of the address. (`default` or `primary`) | | # Animals ## Get All Animals > Request ```python import requests endpoint = 'https://api-staging.smaxtec.com/integration/v2' organisation_id = '123456qwertz' optional_parameters = '?include_archived=false' route = endpoint + '/organisations/' + organisation_id + '/animals' + optional_parameters token = 'yx2zvuB8JD8ppwGti84OT8Muq5eiB2b2EZqsqC-HOXUvLSg' user_agent = 'HerdManagerSoftwareXYZ/2.4' headers = { 'accept': 'application/json', 'User-Agent': user_agent, 'Authorization': 'bearer ' + token } r = requests.get(route, headers=headers) status_code = r.status_code all_animals = r.json() ``` ```bash curl -X GET "[endpoint]/organisations/[organisation_id]/animals" \ -H "accept: application/json" \ -H "Authorization: bearer [token]" \ -H "User-Agent: [user_agent]" ``` > Response example ```json [ { "_id": "5c480ab3314724e123456789", "archived": false, "birthday": "2019-01-10T13:04:52+00:00", "created_at": "2019-01-23T06:33:24+00:00", "current_device_id": "0700000001", "display_name": "92 - susi", "group_id": "57920fca506d993asdfghjkl", "lactation_status": "Young_Cow", "location": "stall", "mark": "92", "mixed_race": [{"race": "ANGLER", "percent": 22}, {"race": "FLECKVIEW", "percent": 78}], "name": "susi", "official_id": "AT111111112", "official_id_rule": "AT", "organisation_id": "123456qwertz", "race": "mixed", "tags": ["mastitis"] } ] ``` This endpoint retrieves from a provided `organisation_id` all animals. **HTTP Request** `GET "[endpoint]/organisations/[organisation_id]/animals"` **URL Parameters** | Parameter | Description | | | ---------------- | --------------------------------------------------- | ---------------- | | organisation_id | ID of the organisation where the animal belongs to. | `required` | | include_archived | Include archived animals. | default: `false` | ## Get Single Animal > Request ```python import requests endpoint = 'https://api-staging.smaxtec.com/integration/v2' organisation_id = '123456qwertz' official_id = 'AT111111112' route = endpoint + '/organisations/' + organisation_id + '/animals/' + official_id token = 'yx2zvuB8JD8ppwGti84OT8Muq5eiB2b2EZqsqC-HOXUvLSg' user_agent = 'HerdManagerSoftwareXYZ/2.4' headers = { 'accept': 'application/json', 'User-Agent': user_agent, 'Authorization': 'bearer ' + token } r = requests.get(route, headers=headers) status_code = r.status_code animal = r.json() ``` ```bash curl -X GET "[endpoint]/organisations/[organisation_id]/animals/[official_id]" \ -H "accept: application/json" \ -H "Authorization: bearer [token]" \ -H "User-Agent: [user_agent]" ``` > Response example ```json { "_id": "5c480ab3314724e123456789", "archived": false, "birthday": "2019-01-10T13:04:52+00:00", "created_at": "2019-01-23T06:33:24+00:00", "current_device_id": "0700000001", "display_name": "92 - susi", "group_id": "57920fca506d993asdfghjkl", "lactation_status": "Young_Cow", "location": "stall", "mark": "92", "mixed_race": [{"race": "ANGLER", "percent": 22}, {"race": "FLECKVIEW", "percent": 78}], "name": "susi", "official_id": "AT111111112", "official_id_rule": "AT", "organisation_id": "123456qwertz", "race": "mixed", "tags": ["mastitis"] } ``` This endpoint retrieves from a provided `organisation_id` and `official_id` the animal. **HTTP Request** `GET "[endpoint]/organisations/[organisation_id]/animals/[official_id]"` **URL Parameters** | Parameter | Description | | | --------------- | ---------------------------------------------------------------------------------- | ---------- | | organisation_id | ID of the organisation where the animal belongs to. | `required` | | official_id | The official id of the animal. This is in the most cases the eartag of the animal. | `required` | ## Create/Update Single Animal > Request ```python import requests endpoint = 'https://api-staging.smaxtec.com/integration/v2' organisation_id = '123456qwertz' official_id = 'AT111111112' route = endpoint + '/organisations/' + organisation_id + '/animals/' + official_id data = { "name": "Strolcha", "group_id": "57920fca506d993asdfgh123", "birthday": "2019-01-10T13:04:52+00:00", "race": "mixed", "location": "stall", "_id": "5c480ab3314724e123456789", "official_id_rule": "AT", "display_name": "92 - susi", "archived": False, "created_at": "2019-01-23T06:33:24+00:00", "official_id": "AT111111112", "lactation_status": "Young_Cow", "current_device_id": "0700000001", "mark": "92", "tags": ["mastitis"], "mixed_race": [{"race": "ANGLER", "percent": 22}, {"race": "FLECKVIEW", "percent": 78}], "organisation_id": "123456qwertz" } token = 'yx2zvuB8JD8ppwGti84OT8Muq5eiB2b2EZqsqC-HOXUvLSg' user_agent = 'HerdManagerSoftwareXYZ/2.4' headers = { 'accept': 'application/json', 'User-Agent': user_agent, 'Authorization': 'bearer ' + token } r = requests.put(route, json=data, headers=headers) status_code = r.status_code animal = r.json() ``` ```bash curl -X PUT "[endpoint]/organisations/[organisation_id]/animals/[official_id]" \ -H "accept: application/json" \ -H "Authorization: bearer [token]" \ -H "Content-Type: application/json" \ -H "User-Agent: [user_agent]"\ -d "{ \"name\": \"Strolcha\", \"group_id\": \"57920fca506d993asdfgh123\", \"birthday\": \"2019-01-10T13:04:52+00:00\", \"race\": \"mixed\", \"location\": \"stall\", \"_id\": \"5c480ab3314724e123456789\", \"official_id_rule\": \"AT\", \"display_name\": \"92 - susi\", \"archived\": false, \"created_at\": \"2019-01-23T06:33:24+00:00\", \"official_id\": \"AT111111112\", \"lactation_status\": \"Young_Cow\", \"current_device_id\": \"0700000001\", \"mark\": \"92\", \"tags\": [\"sold\"], \"mixed_race\": [{\"race\": \"ANGLER\", \"percent\": 22}, {\"race\": \"FLECKVIEW\", \"percent\": 78}],, \"organisation_id\": \"123456qwertz\"}" ``` > Response example ```json { "_id": "5c480ab3314724e123456789", "archived": false, "birthday": "2019-01-10T13:04:52+00:00", "created_at": "2019-01-23T06:33:24+00:00", "current_device_id": "0700000001", "display_name": "92 - Strolcha", "group_id": "57920fca506d993asdfghjkl", "lactation_status": "Young_Cow", "location": "stall", "mark": "92", "mixed_race": [{"race": "ANGLER", "percent": 22}, {"race": "FLECKVIEW", "percent": 78}], "name": "Strolcha", "official_id": "AT111111112", "official_id_rule": "AT", "organisation_id": "123456qwertz", "race": "mixed", "tags": ["mastitis"] } ``` This endpoint creates/updates an animal which is in the organisation with `organisation_id` and the `official_id`. If the animal is created or updated depends. If the animal with the provided `official_id` exists in the organisation, it gets updated. Otherwise the animal gets created. The animal response can be used as a input for these call and just the parameters that are needed to be updated can be replaced. **HTTP Request** `PUT "[endpoint]/organisations/[organisation_id]/animals/[official_id]"` **URL Parameters** | Parameter | Description | | | ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------ | | organisation_id | ID of the organisation where the animal belongs to. | `required` | | official_id | The official id of the animal. This is in the most cases the eartag of the animal. | `required` | | | | _id | Internal ID for the animal. Can't be changed. | | archived | When the animal is archived (inactive) the archived is set to `true`. | | birthday | Day of birth of the animal. | | created_at | The creation time of the animal in the smaXtec system. Can't be changed. | | current_device_id | The ID of the device which is currently active in the animal. | | display_name | Composition of the official ID and the name of the animal. | | group_id | ID of the group where the animal is currently in. | | lactation_status | Status of the cow. Possible parameters: `Young_Cow`, `Lactating_Cow`, `Dry_Cow`. Changes according to events. | | location | Location where the cow currently is. | | mark | Animal number. | `required` for creation. | | mixed_race | When the animal is a breed of two or more races. Example: `"mixed_race": [{"race": "ANGLER", "percent": 22}, ` `{"race": "FLECKVIEW", "percent": 78}]`. The percent needs to sum up to 100. If mixed race is set `"race": "mixed"`. | | name | Name of the animal. | | official_id | Official ID (ear tag) of the animal. Needs to be unique in the organisation. If the official_id is in the data of the PUT method and is different from the route the official_id gets updated. | | official_id_rule | The rule how the official_id should be formatted/stored. Possible parameters: `AT`, `BE`, `BG`, etc. (country code). | | organisation_id | ID of the organisation where the animal belongs to. | | race | Race of the animal. | | tags | Tags which can be given to the animals. Example: `"tags": ["mastitis"]`. | ## Get Animal Metrics > Request ```python import requests endpoint = 'https://api-staging.smaxtec.com/integration/v2' organisation_id = '123456qwertz' official_id = 'AT111111112' route = endpoint + '/organisations/' + organisation_id + '/animals/' + official_id + '/metrics' token = 'yx2zvuB8JD8ppwGti84OT8Muq5eiB2b2EZqsqC-HOXUvLSg' user_agent = 'HerdManagerSoftwareXYZ/2.4' headers = { 'accept': 'application/json', 'User-Agent': user_agent, 'Authorization': 'bearer ' + token } r = requests.get(route, headers=headers) status_code = r.status_code animal = r.json() ``` ```bash curl -X GET "[endpoint]/organisations/[organisation_id]/animals/[official_id]/metrics" \ -H "accept: application/json" \ -H "Authorization: bearer [token]" \ -H "Content-Type: application/json" \ -H "User-Agent: [user_agent]" ``` > Response example ```json [ { "metric": "temp", "available_units": [ "degree_celsius", "degree_fahrenheit" ] }, { "metric": "act", "available_units": [ "act" ] }, { "metric": "act_index", "available_units": [ "percent" ] } ] ``` This Endpoint retrieves all metrics and the corresponding available units from an animal which is in the organisation with `organisation_id` and the `official_id`. **HTTP Request** `GET "[endpoint]/organisations/[organisation_id]/animals/[official_id]/metrics"` **URL Parameters** | Parameter | Description | | | --------------- | ---------------------------------------------------------------------------------- | ---------- | | organisation_id | ID of the organisation where the animal belongs to. | `required` | | official_id | The official id of the animal. This is in the most cases the eartag of the animal. | `required` | **Available Metrics** | Metric | Visible in messenger | Short description | Unit | | ------------------------- | ---------------------- | ---------------------------------------------------------------------------------------------------------- | --------------------------------- | | act_index | ✓ | Smoothed version of `act` (rolling mean) | percent | | temp | ✓ | Temperature | degree_celsius, degree_fahrenheit | | temp_normal_index | ✓ | Normal temperature of the animal calculated by 70% of `temp_without_drink_cycles` in the last 5d. | degree_celsius, degree_fahrenheit | | heat_index | ✓ | Used for thresholding for the `heat` events | percent | | calving_index | ✓ | Used for thresholding for the `calving_detection` events | percent | | ph | ✓ `premium bolus only` | pH value | ph | | rum_index | ✓ `SX.2 only` | The rolling time over the last 24 hours where the animal was ruminating | seconds, minutes, percent | | act | ✕ | Activity | act | | act_heat_index_smart | ✕ | Smoothed current selected heat algorithm | percent | | drink_cycles_v2 | ✕ | Detect a spike in the temperature that is considered as a drinking phase | number | | temp_dec_index | ✕ | A simple outlier detection based on the difference between two moving average filters of different lengths | number | | temp_height_index | ✕ | The difference between `temp_normal_index` and `temp_without_drink_cycles` | degree_celsius, degree_fahrenheit | | temp_inc_index | ✕ | Not available anymore | number | | temp_without_drink_cycles | ✕ | Fast decreases in the temperature signal (drink spikes) | degree_celsius, degree_fahrenheit | ## Get Animal Data > Request ```python import requests endpoint = 'https://api-staging.smaxtec.com/integration/v2' organisation_id = '123456qwertz' official_id = 'AT111111112' route = endpoint + '/organisations/' + organisation_id + '/animals/' + official_id + '/data.json' token = 'yx2zvuB8JD8ppwGti84OT8Muq5eiB2b2EZqsqC-HOXUvLSg' user_agent = 'HerdManagerSoftwareXYZ/2.4' headers = { 'accept': 'application/json', 'User-Agent': user_agent, 'Authorization': 'bearer ' + token } data = { "metrics": ["temp", "act"], "from_date": "2019-02-01T08:21:33+0000", "to_date": "2019-02-01T12:22:16+0000" } r = requests.get(route, data=data, headers=headers) status_code = r.status_code animal = r.json() ``` ```bash curl -X GET "[endpoint]/organisations/[organisation_id]/animals/[official_id]/data.json" \ -H "accept: application/json" \ -H "Authorization: bearer [token]" \ -H "Content-Type: application/json" \ -H "User-Agent: [user_agent]" \ -d "{ \"metrics\": [\"temp\", \"act\"], \"from_date\": \"2019-02-01T08:21:33+0000\", \"to_date\": \"2019-02-01T12:22:16+0000\"}" ``` > Response example ```json [ {"metric": "temp", "data": [ ["2019-02-01T09:00:00+01:00", 38.13 ], ["2019-02-01T10:00:00+01:00", 38.52 ], ["2019-02-01T11:00:00+01:00", 38.85 ], ["2019-02-01T12:00:00+01:00", 36.89 ], ["2019-02-01T13:00:00+01:00", 37.6 ] ], "unit": "degree_celsius" }, {"metric": "act", "data": [ ["2019-02-01T09:00:00+01:00", 3.35 ], ["2019-02-01T10:00:00+01:00", 3.31 ], ["2019-02-01T11:00:00+01:00", 3.46 ], ["2019-02-01T12:00:00+01:00", 3.99 ], ["2019-02-01T13:00:00+01:00", 4.3 ] ], "unit": "act" } ] ``` This endpoint retrieves from a provided `organisation_id` and `official_id` data from its sensor. The response depends on the provided list of `metrics` and the period. **HTTP Request** `GET "[endpoint]/organisations/[organisation_id]/animals/[official_id]/data.json"` **URL Parameters** | Parameter | Description | | | ------------------ | ----------------------------------------------------------------------------------------- | ---------- | | organisation_id | ID of the organisation where the animal belongs to. | `required` | | official_id | The official id of the animal. This is in the most cases the eartag of the animal. | `required` | | | | | | metrics | The list of metrics where data is wanted. | `required` | | from_date | The start date from the period where data is wanted. | `required` | | to_date | The end date from the period where data is wanted. | `required` | | aggregation_period | The period of data points. Either 10 minutes or 1 hour. | | | preferred_units | The units which are preferred. For example: "act", "degree_celsius", "degree_fahrenheit". | | # Events Occurrences which arise for an animal are stored in the **events**. These events include reproduction events, health events, feeding events etc.. All events can be fetched but just events of the type `heat`, `insemination`, `pregnancy_result`, `dry_off`, `calving_confirmation`, `abort` and `diagnosis` can be created via the API. Additional information regarding the event type can be added. All other events are generated by the smaXtec system. ## Get Events by Organisation > Request ```python import requests endpoint = 'https://api-staging.smaxtec.com/integration/v2' organisation_id = '123456qwertz' route = endpoint + '/organisations/' + organisation_id + '/events' token = 'yx2zvuB8JD8ppwGti84OT8Muq5eiB2b2EZqsqC-HOXUvLSg' user_agent = 'HerdManagerSoftwareXYZ/2.4' headers = { 'accept': 'application/json', 'User-Agent': user_agent, 'Authorization': 'bearer ' + token } data = { "min_create_ts": "2019-07-30T12:22:16", "min_event_ts": "2019-07-21T12:22:16" } r = requests.get(route, data=data, headers=headers) status_code = r.status_code all_animal_events = r.json() ``` ```bash curl -X GET "[endpoint]/organisations/[organisation_id]/events?min_create_ts=2019-07-30T13%3A04%3A52&min_event_ts=2019-07-21T13%3A04%3A52" \ -H "accept: application/json" \ -H "Authorization: bearer [token]" \ -H "User-Agent: [user_agent]" ``` > Response example ```json [ { "_id": "5b61e5bd90e6e1d84e4a2123", "animal_id": "5c480ab3314724e123456789", "create_ts": "2020-03-23T16:54:21+00:00", "event_ts": "2020-03-23T00:00:00+00:00", "event_type": "calving_confirmation", "number": 3 }, { "_id": "5b61e5bdb493c3931a260123", "animal_id": "5c480ab3314724e123456790", "create_ts": "2020-02-01T16:54:21+00:00", "event_ts": "2020-02-01T01:00:00+00:00", "event_type": "information_update" }, { "_id": "5b61eb7e2782f75791c5e123", "animal_id": "5c480ab3314724e123456791", "create_ts": "2020-01-01T17:18:54+00:00", "event_ts": "2020-01-01T00:00:00+00:00", "event_type": "heat", "cycle_length": 300 }, { "_id": "5b61ed2c19cd8518817d6123", "animal_id": "5c480ab3314724e123456789", "create_ts": "2020-03-01T17:26:04+00:00", "event_ts": "2020-03-01T20:13:00+00:00", "event_type": "insemination", "days_to_calving": 275 }, { "_id": "5b61ed2c041922c1f7030123", "animal_id": "5c480ab3314724e123456790", "create_ts": "2019-08-01T17:26:04+00:00", "event_ts": "2019-07-22T23:13:00+00:00", "event_type": "pregnancy_result", "pregnant": true, "expected_calving_date": "2020-04-23T12:00:00+00:00", "insemination_date": "2018-07-22T20:13:00+00:00" }, { "_id": "5ae62c4ad591117f095f4123", "animal_id": "5c480ab3314724e123456789", "create_ts": "2020-02-01 21:00:00", "event_ts": "2020-02-01 21:00:00", "event_type": "health_106" } ] ``` This endpoint retrieves from a provided `organisation_id` the events of the animals. **HTTP Request** `GET "[endpoint]/organisations/[organisation_id]/events"` **URL Parameters** | Parameter | Description | | | --------------- | --------------------------------------------------- | ---------- | | organisation_id | ID of the organisation where the animal belongs to. | `required` | | min_create_ts | The minimum creation timestamp of the events. | | min_event_ts | The minimum event timestamp of the events. | ## Get Events by official_id > Request ```python import requests endpoint = 'https://api-staging.smaxtec.com/integration/v2' organisation_id = '123456qwertz' official_id = 'AT111111112' route = endpoint + '/organisations/' + organisation_id + '/animals/' + official_id + '/events' token = 'yx2zvuB8JD8ppwGti84OT8Muq5eiB2b2EZqsqC-HOXUvLSg' user_agent = 'HerdManagerSoftwareXYZ/2.4' headers = { 'accept': 'application/json', 'User-Agent': user_agent, 'Authorization': 'bearer ' + token } data = { "min_create_ts": "2016-07-30T12:22:16", "min_event_ts": "2016-07-21T12:22:16" } r = requests.get(route, data=data, headers=headers) status_code = r.status_code all_animal_events = r.json() ``` ```bash curl -X GET "[endpoint]/organisations/[organisation_id]/animals/[official_id]/events?min_create_ts=2016-07-30T13%3A04%3A52&min_event_ts=2016-07-21T13%3A04%3A52" \ -H "accept: application/json" \ -H "Authorization: bearer [token]" \ -H "User-Agent: [user_agent]" ``` > Response example ```json [ { "_id": "5b61e5bd90e6e1d84e4a2123", "animal_id": "5c480ab3314724e123456789", "create_ts": "2018-08-01T16:54:21+00:00", "event_ts": "2015-03-23T00:00:00+00:00", "event_type": "calving_confirmation", "number": 3 }, { "_id": "5b61e5bdb493c3931a260123", "animal_id": "5c480ab3314724e123456789", "create_ts": "2018-08-01T16:54:21+00:00", "event_ts": "2015-03-23T01:00:00+00:00", "event_type": "information_update" }, { "_id": "5b61eb7e2782f75791c5e123", "animal_id": "5c480ab3314724e123456789", "create_ts": "2018-08-01T17:18:54+00:00", "event_ts": "2017-05-15T00:00:00+00:00", "event_type": "heat", "cycle_length": 300 }, { "_id": "5b61ed2c19cd8518817d6123", "animal_id": "5c480ab3314724e123456789", "create_ts": "2018-08-01T17:26:04+00:00", "event_ts": "2017-07-22T20:13:00+00:00", "event_type": "insemination", "days_to_calving": 275 }, { "_id": "5b61ed2c041922c1f7030123", "animal_id": "5c480ab3314724e123456789", "create_ts": "2018-08-01T17:26:04+00:00", "event_ts": "2017-07-22T23:13:00+00:00", "event_type": "pregnancy_result", "pregnant": true, "expected_calving_date": "2018-04-23T12:00:00+00:00", "insemination_date": "2017-07-22T20:13:00+00:00" }, { "_id": "5ae62c4ad591117f095f4123", "animal_id": "5c480ab3314724e123456789", "create_ts": "2018-04-29 21:00:00", "event_ts": "2018-04-29 21:00:00", "event_type": "health_106" } ] ``` This endpoint retrieves from a provided `organisation_id` and `official_id` the events of an animal. **HTTP Request** `GET "[endpoint]/organisations/[organisation_id]/animals/[official_id]/events"` **URL Parameters** | Parameter | Description | | | --------------- | ---------------------------------------------------------------------------------- | ---------- | | organisation_id | ID of the organisation where the animal belongs to. | `required` | | official_id | The official id of the animal. This is in the most cases the eartag of the animal. | `required` | | min_create_ts | The minimum creation timestamp of the events. | | min_event_ts | The minimum event timestamp of the events. | **Event Types** The smaXtec system has the following event types. | Event Type | Description | | -------------------- | ------------------------------------------------- | | heat | Detection of a heat | | insemination | Inseminated of an animal | | pregnancy_result | A positive or negative pregnancy result | | calving_detection | Detection of a calving | | dry_off | Dry off | | calving_confirmation | Confirmation of a calving | | waiting_for_calving | Few days before calving | | abort | Abortion of a pregnancy which can be a late abort | | information_update | Updating information | | diagnosis | Diagnose | | health_101 | Insufficient water intake | | health_102 | Increase in drinking cycles | | health_103 | Reduced drinking cycles | | health_104 | Temperature increase | | health_106 | Temperature drop | | health_301 | Rumination decrease and cow is dry | | health_302 | Rumination decrease and cow is close up | | health_303 | Rumination decrease and cow is around calving | | health_304 | Rumination decrease and cow is a fresh cow | | health_305 | Rumination decrease and cow is lactating | | health_601 | THI ≥ 72 Heat stress | | health_602 | THI ≥ 78 Heat stress | | health_603 | THI ≥ 82 Heat stress | | health_703 | Drop in activity | | feeding_201 | Feed efficiency | | feeding_202 | Risk of acidosis | | feeding_203 | Increase in average pH | | feeding_204 | Drop in average pH | | feeding_205 | Increase in 12h pH | | feeding_206 | Drop in 12h pH | | fertility_105 | Indication of imminent calving | | actincrease_701 | Increase in activity | | actincrease_704 | Increase in activity | ## Create Events > Request ```python import requests endpoint = 'https://api-staging.smaxtec.com/integration/v2' organisation_id = '123456qwertz' official_id = 'AT111111112' route = endpoint + '/organisations/' + organisation_id + '/animals/' + official_id + '/events' data = { "events": [ { "event_type": "insemination", "event_ts": "2019-01-18T12:00:00+00:00", "days_to_calving": 275 } ] } token = 'yx2zvuB8JD8ppwGti84OT8Muq5eiB2b2EZqsqC-HOXUvLSg' user_agent = 'HerdManagerSoftwareXYZ/2.4' headers = { 'accept': 'application/json', 'User-Agent': user_agent, 'Authorization': 'bearer ' + token } r = requests.put(route, json=data, headers=headers) status_code = r.status_code all_animal_events = r.json() ``` ```bash curl -X PUT "[endpoint]/organisations/[organisation_id]/animals/[official_id]/events" \ -H "accept: application/json" \ -H "Authorization: bearer [token]" \ -H "User-Agent: [user_agent]" \ -d "{\"events\": [{\"event_type\": \"insemination\", \"event_ts\": \"2019-01-18T12:00:00+00:00\", \"days_to_calving\": 275}]}" ``` > Response example (will change) ```json [ { "_id": "5c584ba651945498be341123", "animal_id": "5c480ab3314724e123456789", "create_ts": "2019-02-04T14:26:46+00:00", "event_ts": "2019-01-18T12:00:00+00:00", "event_type": "insemination", "days_to_calving": 275 } ] ``` This endpoint creates events for an animal with the given `official_id` which belongs to the organisation with the given `organisation_id`. If the event is created it depends on the `event_type` and the `event_ts`. If the event with this two parameters does not exist, it gets created. Otherwise the event is skipped. It is possible to add just the events to the data which should be added to the smaXtec system or add just all events from your system and the smaXtec system adds those which are not in the system. <aside class="notice">Just events of the type <b>heat</b>, <b>insemination</b>, <b>pregnancy_result</b>, <b>dry_off</b>, <b>calving_confirmation</b>, <b>abort</b> and <b>diagnosis</b> can be created via the API.</aside> **HTTP Request** `PUT "[endpoint]/organisations/[organisation_id]/animals/[official_id]/events"` **URL Parameters** | Parameter | Description | | | ----------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- | | organisation_id | The ID of the organisation which the animals belong to. | `required` | | official_id | The official id of the animal. This is in the most cases the eartag of the animal. | `required` | | | | | | _id | ID of the Event in the smaXtec system. | | | animal_id | ID of the Animal in the smaXtec system. | | | create_ts | Time when the event was created on our server. | | | event_ts | Time when the event actually happened. | | | event_type | Type of the event. | | | | | | | **heat Parameters** | | | | cycle_length | Length of the current cycle. | | | reason | The reason why the heat was added. | | | | | | | **insemination Parameters** | | | | days_to_calving | Days from the insemination until the expected calving date. Default: `280` | | | | | | | **pregnancy_result Parameters** | | | | expected_calving_date | Date when the calving is expected. | | | insemination_date | Date of the insemination which led to the pregnancy result. If no prior insemination on that date is saved an insemination event on that date will be created. | | | pregnant | If the pregnancy result was positive (true) or negative (false). | | | | | | | **calving_confirmation Parameters** | | | | number | Number of calvings. | | | | | | | **abort Parameters** | | | | late_abort | When the cow was long enough pregnant so that the cow is lactating then `late_abort` is `true`. | | | | | | | **diagnosis Parameters** | | | | icar_key | ICAR key for the diagnosis. | | | diagnosis_key | If an own key for diagnosis is used, it should be set here. | | | diagnosis_key_type | If an own key for diagnosis is used, a type of the diagnosis_key should be defined. eg.: `MY_OWN_KEY_DEFINITION_SYSTEM` | | # Devices Devices are all sensors which measure data. ## Get All Devices > Request ```python import requests endpoint = 'https://api-staging.smaxtec.com/integration/v2' organisation_id = '123456qwertz' route = endpoint + '/organisations/' + organisation_id + '/devices' data = { 'device_type': 'all' } token = 'yx2zvuB8JD8ppwGti84OT8Muq5eiB2b2EZqsqC-HOXUvLSg' user_agent = 'HerdManagerSoftwareXYZ/2.4' headers = { 'accept': 'application/json', 'User-Agent': user_agent, 'Authorization': 'bearer ' + token } r = requests.get(route, json=data, headers=headers) status_code = r.status_code all_devices = r.json() ``` ```bash curl -X GET "[endpoint]/organisations/[organisation_id]/devices?device_type=all" \ -H "accept: application/json" \ -H "Authorization: bearer [token]" \ -H "User-Agent: [user_agent]" ``` > Response example ```json [ "0600000001", "0600000002", "0200000001", "0700000001" ] ``` This call delivers all devices of the given organisation if the parameter 'all' is used, Otherwise this call returns just the climate sensors (06) for the given organisation. **HTTP Request** `GET "[endpoint]/organisations/[organisation_id]/devices"` **URL Parameters** | Parameter | Description | | | --------------- | --------------------------------------------------- | ---------- | | organisation_id | ID of the organisation where the animal belongs to. | `required` | | device_type | 'all' represents all devices. | ## Get Device Stats > Request ```python import requests endpoint = 'https://api-staging.smaxtec.com/integration/v2' organisation_id = '123456qwertz' device_id = '0200000001' route = endpoint + '/organisations/' + organisation_id + '/devices/' + device_id token = 'yx2zvuB8JD8ppwGti84OT8Muq5eiB2b2EZqsqC-HOXUvLSg' user_agent = 'HerdManagerSoftwareXYZ/2.4' headers = { 'accept': 'application/json', 'User-Agent': user_agent, 'Authorization': 'bearer ' + token } r = requests.get(route, headers=headers) status_code = r.status_code device = r.json() ``` ```bash curl -X GET "[endpoint]/organisations/[organisation_id]/devices/[device_id]" \ -H "accept: application/json" \ -H "Authorization: bearer [token]" \ -H "User-Agent: [user_agent]" ``` > Response example ```json { "organisation_id": "569e0bcea80a5f1c07b5430f", "_id": "0700007154", "last_readout": { "timestamp": "2019-11-14T12:22:16", "readout_id": "0200000041", "basestation_id": "0200000041" } } ``` This call delivers data about the last readout. <aside class="warning"> To get the last readout you must use live smaXtec system! </aside> **HTTP Request** `GET "[endpoint]/organisations/[organisation_id]/devices/[device_id]"` **URL Parameters** | Parameter | Description | | | --------------- | --------------------------------------------------- | ---------- | | organisation_id | ID of the organisation where the animal belongs to. | `required` | | device_id | ID of the device | `required` | ## Get Device Data > Request ```python import requests endpoint = 'https://api-staging.smaxtec.com/integration/v2' organisation_id = '123456qwertz' device_id = '0600000001' route = endpoint + '/organisations/' + organisation_id + '/devices/' + device_id + '/data.json' token = 'yx2zvuB8JD8ppwGti84OT8Muq5eiB2b2EZqsqC-HOXUvLSg' user_agent = 'HerdManagerSoftwareXYZ/2.4' headers = { 'accept': 'application/json', 'User-Agent': user_agent, 'Authorization': 'bearer ' + token } data = { "metrics": ["temp", "hum"], "preferred_units": ["degree_celsius"], "from_date": "2019-06-01T12:22:16", "to_date": "2019-06-02T12:22:16", "timestamp_format": "iso", "aggregation_period": "hourly" } r = requests.get(route, data=data, headers=headers) status_code = r.status_code device_data = r.json() ``` ```bash curl -X GET "[endpoint]/organisations/[organisation_id]/devices/[device_id]/data.json?to_date=2019-06-20T13%3A04%3A52&aggregation_period=hourly&metrics=temp&timestamp_format=iso&from_date=2019-04-20T13%3A04%3A52" \ -H "accept: application/json" \ -H "Authorization: bearer [token]" \ -H "User-Agent: [user_agent]" ``` > Response example ```json [ { "metric": "temp", "unit": "degree_celsius", "data": [ [ "2019-06-01T12:23:00+00:00", 20.77 ], [ "2019-06-01T12:33:00+00:00", 21.34 ], [ "2019-06-01T12:43:00+00:00", 21.66 ] ] }, { "metric": "hum", "unit": "percent", "data": [ [ "2019-06-01T12:23:00+00:00", 87.1 ], [ "2019-06-01T12:33:00+00:00", 83.6 ], [ "2019-06-01T12:43:00+00:00", 84.9 ] ] } ] ``` This endpoint retrieves from a specific `organisation_id` and `device_id` the corresponding data. The response depends furthermore on the list of provided `metrics` and the period of time. **HTTP Request** `GET "[endpoint]/organisations/[organisation_id]/devices/[device_id]/data.json"` **URL Parameters** | Parameter | Description | | | ------------------ | ----------------------------------------------------------------------------------------- | ---------- | | organisation_id | ID of the organisation where the animal belongs to. | `required` | | device_id | The ID of the device. | `required` | | | | | | metrics | The list of metrics which are wanted. | `required` | | from_date | The start date from the period of data. | `required` | | to_date | The end date from the period of data. | `required` | | timestamp_format | The format of the provided time stamps. (`iso`, `utc`, `local` or `tuple`) | | | aggregation_period | The period of data points. Either 10 minutes or 1 hour. (`10minutes` or `hourly`) | | | preferred_units | The units which are preferred. For example: `act`, `degree_celsius`, `degree_fahrenheit`. | | # Translations The translated text for events or specific events can be accessed over the integration API. ## Get all Event Translations > Request ```python import requests endpoint = 'https://api-staging.smaxtec.com/integration/v2' language = 'en' route = endpoint + '/translations/' + language + '/events' token = 'yx2zvuB8JD8ppwGti84OT8Muq5eiB2b2EZqsqC-HOXUvLSg' user_agent = 'HerdManagerSoftwareXYZ/2.4' headers = { 'accept': 'application/json', 'User-Agent': user_agent, 'Authorization': 'bearer ' + token } r = requests.get(route, headers=headers) status_code = r.status_code event_text = r.json() ``` ```bash curl -X GET "[endpoint]/translations/[language]/events" \ -H "accept: application/json" \ -H "Authorization: bearer [token]" \ -H "User-Agent: [user_agent]" ``` > Response example ```json { "EVENT": { "HEALTH_101": { "TITLE": "Indication of too few daily drinking cycles ({{value | number:0}})", "DESCRIPTION": "On {{event_ts | timestamp:'dddd, ll'}} the number of drinking cycles was {{value | number:0}}. <br \/>Please check provision of water and state of health (e.g. heat stress).", "KEYWORD": "Insufficient water intake" }, "HEALTH_102": { "TITLE": "Indication of an increase in number of drinking cycles compared with the previous day by {{value | number: 0}}", "DESCRIPTION": "On {{event_ts | timestamp:'dddd, ll'}} the animal drank {{value | number:0}} times more than the previous day. <br \/>Please check animal's state of health and possible heat stress.", "KEYWORD": "Increase in drinking cycles" } } } ``` With this call translations for the animal events can be accessed for various languages. The translations contain for each event a `KEYWORD`, a `TITLE` and a `DESCRIPTION`. <aside class="notice">Current available languages: <b>de, en-au, en, es, fr, hr, hu, it, ko, lv, nl, pl, pt, ro, ru, sl, tr, uk, zh-cn</b></aside> **HTTP Request** `GET "[endpoint]/translations/[language]/events"` **Response** | Key | Description | | ------------- | ------------------------------------- | | `KEYWORD` | Keywords for the event translation. | | `TITLE` | Short description. | | `DESCRIPTION` | Detailed information about the event. | ## Get single Event Translations > Request ```python import requests endpoint = 'https://api-staging.smaxtec.com/integration/v2' language = 'en' event_type = 'health_102' route = endpoint + '/translations/' + language + '/events/' + event_type token = 'yx2zvuB8JD8ppwGti84OT8Muq5eiB2b2EZqsqC-HOXUvLSg' user_agent = 'HerdManagerSoftwareXYZ/2.4' headers = { 'accept': 'application/json', 'User-Agent': user_agent, 'Authorization': 'bearer ' + token } r = requests.get(route, headers=headers) status_code = r.status_code health_102_text = r.json() ``` ```bash curl -X GET "[endpoint]/translations/[language]/events/[event_type]" \ -H "accept: application/json" \ -H "Authorization: bearer [token]" \ -H "User-Agent: [user_agent]" ``` > Response example ```json { "EVENT": { "health_102": { "DESCRIPTION": "On {{event_ts | timestamp:'dddd, ll'}} the animal drank {{value | number:0}} times more than the previous day. <br />Please check animal's state of health and possible heat stress.", "KEYWORD": "Increase in drinking cycles", "TITLE": "Indication of an increase in number of drinking cycles compared with the previous day by {{value | number: 0}}" } } } ``` It is also possible to access the translation for just a single event. **HTTP Request** `GET "[endpoint]/translations/[language]/events/[event_type]"`

43.020503

653

0.495734

eng_Latn

0.733996

e964d07853ca9661a485847c940badd7ce0a3e63

107

md

Markdown

docs/src/reference.md

KristofferC/ProfileSVG.jl

327758638e6370acb6e71c2fdc8bd2b6efe5d55e

[ "MIT" ]

41

2020-05-04T10:34:00.000Z

2022-03-24T18:39:47.000Z

docs/src/reference.md

KristofferC/ProfileSVG.jl

327758638e6370acb6e71c2fdc8bd2b6efe5d55e

[ "MIT" ]

58

2020-04-29T16:28:28.000Z

2022-02-18T00:10:28.000Z

docs/src/reference.md

KristofferC/ProfileSVG.jl

327758638e6370acb6e71c2fdc8bd2b6efe5d55e

[ "MIT" ]

4

2020-02-08T11:55:03.000Z

2020-04-28T11:43:50.000Z

# Reference ```@docs @profview ProfileSVG.view ProfileSVG.save ProfileSVG.set_default ProfileSVG.init ```

10.7

22

0.785047

yue_Hant

0.446297

e9654866e46db1490744474b491a634bf804e907

17

md

Markdown

Note.md

TangYin777/basic

896b514baab189a502641c4aa5ba123629748f2e

[ "MIT" ]

null

Note.md

TangYin777/basic

896b514baab189a502641c4aa5ba123629748f2e

[ "MIT" ]

2

2021-09-29T02:51:34.000Z

2021-09-29T03:16:40.000Z

Note.md

TangYin777/basic

896b514baab189a502641c4aa5ba123629748f2e

[ "MIT" ]

1

2021-09-29T02:27:11.000Z

以下是一些注意事项 bpz修改了

5.666667

9

0.882353

zho_Hans

0.987955

e9654bccad871da54912e995f3349397e83e69a2

156

md

Markdown

docs/zh/setup/index.md

okbug/leoric

9db304a8e962c14835acd038148a526db6b8a8a2

[ "BSD-3-Clause" ]

137

2019-04-03T03:26:25.000Z

2022-03-30T14:11:18.000Z

docs/zh/setup/index.md

okbug/leoric

9db304a8e962c14835acd038148a526db6b8a8a2

[ "BSD-3-Clause" ]

132

2019-03-25T08:50:54.000Z

2022-03-22T12:30:58.000Z

docs/zh/setup/index.md

okbug/leoric

9db304a8e962c14835acd038148a526db6b8a8a2

[ "BSD-3-Clause" ]

18

2019-04-04T08:28:16.000Z

2022-02-23T04:04:25.000Z

--- layout: zh title: 快速配置 --- - [在 Egg / Chair 应用中配置]({{ '/zh/setup/egg' | relative_url }}) - [在 Express 应用中配置]({{ '/zh/setup/express' | relative_url }})

19.5

61

0.589744

yue_Hant

0.185046

e965b081de25c5808f929914f2af5d8eafbaf34b

2,344

md

Markdown

examples/cdk2-example/README.md

hannahbrucemacdonald/perses

6b43d200501e587b352dce5aaefef38e4145048b

[ "MIT" ]

null

examples/cdk2-example/README.md

hannahbrucemacdonald/perses

6b43d200501e587b352dce5aaefef38e4145048b

[ "MIT" ]

null

examples/cdk2-example/README.md

hannahbrucemacdonald/perses

6b43d200501e587b352dce5aaefef38e4145048b

[ "MIT" ]

null

# CDK2 protein-ligand example This folder contains an example setup for a protein-ligand relative free energy calculation. ## Origin of input files The input files in this directory are from the Schrodinger JACS dataset, with the protein pdb fixed using [PDBFixer](https://github.com/pandegroup/pdbfixer). ## File description * CDK2_fixed_nohet.pdb: PDB file for CDK2 structure from JACS benchmark (cited below) run through PDBFixer and pdb4amber. * CDK2_ligands.sdf: SDF file of CDK2 ligands from JACS structure * cdk2_nonequilibrium.yaml: Example configuration file for running CDK2 relative free energy calculations with nonequilibrium switching * cdk2_sams.yaml: Example configuration file for running CDK2 relative free energy calculations with SAMS. * cdk2_repex.yaml: Example configuration file for running CDK2 relative free energy calculations with SAMS. * run.py: Helper script to run a range of pairs in the same job submission script * submit_ligpairs.sh: LSF job submission script for running a range of ligand pairs simultaneously ## Running example The example can be run by calling `python ../../scripts/setup_relative_calculation.py cdk2_sams.yaml`. By default, the included yaml file directs the code to set up and run the solvent phase. The options for the run are contained in the `yaml` file passed to the `setup_relative_calculation.py` script. There are two examples provided, `cdk2_sams.yaml` and `cdk2_nonequilibrium.yaml`, which allow the user to run either a SAMS or nonequilibrium switching-based free energy calculation, respectively. To run a range of ligands, change the ligand indexed in `run.py` to those of interest. In `submit-ligpairs.sh`, change the jobarray so that it is the same length of the list of ligand pairs. To run the job on lilac, or a similar cluster, use `bsub < submit-ligpairs.sh`. ## References Accurate and Reliable Prediction of Relative Ligand Binding Potency in Prospective Drug Discovery by Way of a Modern Free-Energy Calculation Protocol and Force Field Lingle Wang et al. JACS 137:2695, 2017. DOI: http://doi.org/10.1021/ja512751q SI info: http://pubs.acs.org/doi/suppl/10.1021/ja512751q/suppl_file/ja512751q_si_001.pdf SI datasets: https://drive.google.com/drive/u/1/folders/0BylmDElgu6QLTnJ2WGMzNXBENkk This dataset is used for testing relative transformations.

54.511628

192

0.800341

eng_Latn

0.972582

e965cbc9eee39b69ae860cc2f7c23732e9e6b596

53

md

Markdown

README.md

theiseja/javascript-notes

2b56122ea4eb8c5cd7e84ff3493e3ad4b426e9f5

[ "MIT" ]

null

README.md

theiseja/javascript-notes

2b56122ea4eb8c5cd7e84ff3493e3ad4b426e9f5

[ "MIT" ]

null

README.md

theiseja/javascript-notes

2b56122ea4eb8c5cd7e84ff3493e3ad4b426e9f5

[ "MIT" ]

null

# javascript-notes Personal notes while learning JS.

17.666667

33

0.811321

eng_Latn

0.983755

e96742e61a32155796bd746687fe35854c034a70

223

md

Markdown

Tutorial_H3ll/godot-tutorials/parallax-scrolling/README.md

shinspiegel/godot_playgound

b2ef27d283f4bfbd244f0102887b27935d90c9dc

[ "MIT" ]

5

2021-06-13T16:24:05.000Z

2021-12-16T09:33:41.000Z

Tutorial_H3ll/godot-tutorials/parallax-scrolling/README.md

shinspiegel/godot_playgound

b2ef27d283f4bfbd244f0102887b27935d90c9dc

[ "MIT" ]

2

2021-06-30T20:40:10.000Z

2022-02-04T13:47:12.000Z

Tutorial_H3ll/godot-tutorials/parallax-scrolling/README.md

shinspiegel/godot_playgound

b2ef27d283f4bfbd244f0102887b27935d90c9dc

[ "MIT" ]

2

2021-12-16T09:55:06.000Z

2021-12-24T09:32:26.000Z

[![thumbnail](thumbnail.jpg)](https://www.youtube.com/watch?v=f8z4x6R7OSM) # Godot Tutorial: Parallax Scrolling In this tutorial I am going to guide you through the process of adding Parallax Scrolling to your Godot game.

44.6

109

0.784753

eng_Latn

0.919955

e967535aa06d517bcfa9e22a79736b269f820542

914

md

Markdown

README.md

aria16-ghost/ggg-social-app

e2e1ebff3ca7334416d801f380805b2959de57d0

[ "MIT" ]

null

README.md

aria16-ghost/ggg-social-app

e2e1ebff3ca7334416d801f380805b2959de57d0

[ "MIT" ]

null

README.md

aria16-ghost/ggg-social-app

e2e1ebff3ca7334416d801f380805b2959de57d0

[ "MIT" ]

null

# ggg-social-app This is a dummy social media app. Which have the following features: - [ ] User Authentication with Password, Google, FB - [ ] User can post images - [ ] User can follow each other - [ ] News feed - [ ] Private Profiles - [ ] Like and Comment on post. #### Maintaners @ashertoufeeq @1arshan --- ## Running this project #### The App ``` git clone https://github.com/aria16-solutions/ggg-social-app.git cd ggg-social-app/app yarn install yarn start ``` #### The Server ``` git clone https://github.com/aria16-solutions/ggg-social-app.git cd ggg-social-app/api virtualenv venv python=python3.7 . venv/bin/activate pip install requirements.txt ./manage runserver ``` ## Color Scheme and Typography **To be added** by @ashertoufeeq ## API Documentation **To be added** by @1arshan ## App Pages and Screenshorts ``` - Login - Register - Home - User Profile ``` **To be added** by @ashertoufeeq

18.653061

68

0.705689

eng_Latn

0.790514

e967d46ab54d71871083bce43bb06999c12e2497

2,629

markdown

Markdown

_posts/2013-11-23-chocolate-mousse-pie.markdown

amypeniston/blog

f98bc348e9a5e0d21d0eca961690ee89dfc245a9

[ "MIT" ]

null

_posts/2013-11-23-chocolate-mousse-pie.markdown

amypeniston/blog

f98bc348e9a5e0d21d0eca961690ee89dfc245a9

[ "MIT" ]

null

_posts/2013-11-23-chocolate-mousse-pie.markdown

amypeniston/blog

f98bc348e9a5e0d21d0eca961690ee89dfc245a9

[ "MIT" ]

null

--- layout: post title: Chocolate Mousse Pie date: '2013-11-23 02:52:00' --- *This recipe has only a few ingredients, making it very simple to throw together for a special event.* Crust: > 2-3 of your favorite cookies, crumbled (homemade or store-bought) > 1 store-bought pie crust (graham cracker is delicious) Mousse: > 4 ounces semisweet chocolate, chopped > 2 ounces bittersweet chocolate, chopped > 1/4 cup cold heavy cream > 3 large egg whites, room temperature > 3/4 cup cold heavy cream Whipped Cream Topping: > 2 tablespoons white sugar > 1 teaspoon vanilla extract > 1 1/2 cups cold heavy cream > chocolate for garnish * Crack 3 eggs and separate yolks, discarding or using for another dish. Allow the egg whites to come to room temperature in a small bowl. * Open up your store-bought pie crust. Crush 2-3 of your favorite cookies and sprinkle cookie bits on the bottom of the pie crust. Set aside. * Find a saucepan and a glass bowl that fits snugly on top to act as a double boiler. Fill the saucepan with 2 inches of water and bring to a simmer over medium heat. * Place the chopped chocolate and 1/4 cup of cold cream in the double-boiler bowl and melt over heat, stirring frequently with a rubber spatula. Try not to get any moisture in the chocolate mixture as it will seize. Once smooth, remove the chocolate mixture from the heat, and wipe the bottom of the bowl dry. Set aside to cool slightly while you prepare the rest of the filling ingredients. * Beat the egg whites on high speed until stiff peaks form, approximately 1-2 minutes. * Clean the beater attachments and wipe dry. In a separate bowl beat the remaining 3/4 cup of cold heavy cream until thick and fluffy, approximately 1-2 minutes. * Add the whipped cream to the melted chocolate and use a rubber spatula to fold together. Try to be as light-handed as possible. Once the mixture is uniformly streaky with whipped cream, add the egg whites and continue to fold gently. Fold, fold, fold until there are no large blobs of white. Do not overmix! * Spoon the mousse into the pie crust and smooth top. Stick the pie in the fridge to cool for approximately 2 hours, or until set. * Just before you’re ready to eat the pie, place a small metal bowl in your freezer and allow to chill for 10 minutes. * Remove the bowl from your freezer and into it pour 1 1/2 cups cold heavy cream, vanilla and sugar. Beat until soft peaks for, about 1-2 minutes. * Spread the whipped cream over your chilled pie. * To garnish, shave a piece of chocolate over your pie using a cheese grater or carrot peeler. Enjoy!

64.121951

309

0.760365

eng_Latn

0.999383

e9684f534849a607b92a1dd8c54dbefb1632c293

38,121

md

Markdown

treebanks/qtd_sagt/qtd_sagt-feat-Tense.md

MarcoDiMarek/docs

c00f9c59b8e1e93b24c119fbdccb84aaf6b06565

[ "Apache-2.0" ]

null

treebanks/qtd_sagt/qtd_sagt-feat-Tense.md

MarcoDiMarek/docs

c00f9c59b8e1e93b24c119fbdccb84aaf6b06565

[ "Apache-2.0" ]

null

treebanks/qtd_sagt/qtd_sagt-feat-Tense.md

MarcoDiMarek/docs

c00f9c59b8e1e93b24c119fbdccb84aaf6b06565

[ "Apache-2.0" ]

null

--- layout: base title: 'Statistics of Tense in UD_Turkish_German-SAGT' udver: '2' --- ## Treebank Statistics: UD_Turkish_German-SAGT: Features: `Tense` This feature is universal. It occurs with 4 different values: `Fut`, `Past`, `Pqp`, `Pres`. 4139 tokens (13%) have a non-empty value of `Tense`. 1437 types (24%) occur at least once with a non-empty value of `Tense`. 414 lemmas (12%) occur at least once with a non-empty value of `Tense`. The feature is used with 2 part-of-speech tags: <tt><a href="qtd_sagt-pos-VERB.html">VERB</a></tt> (2936; 9% instances), <tt><a href="qtd_sagt-pos-AUX.html">AUX</a></tt> (1203; 4% instances). ### `VERB` 2936 <tt><a href="qtd_sagt-pos-VERB.html">VERB</a></tt> tokens (71% of all `VERB` tokens) have a non-empty value of `Tense`. The most frequent other feature values with which `VERB` and `Tense` co-occurred: <tt><a href="qtd_sagt-feat-Case.html">Case</a></tt><tt>=EMPTY</tt> (2650; 90%), <tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt> (2476; 84%), <tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Ind</tt> (2223; 76%), <tt><a href="qtd_sagt-feat-VerbForm.html">VerbForm</a></tt><tt>=EMPTY</tt> (1820; 62%), <tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Fh</tt> (1491; 51%). `VERB` tokens may have the following values of `Tense`: * `Fut` (134; 5% of non-empty `Tense`): <em>olacak, yapacağım, gideceğiz, yapacaksın, gelecek, bakacağım, başlayacağım, deneyeceğim, diyecektim, gerekecek</em> * `Past` (879; 30% of non-empty `Tense`): <em>yaptım, olduğu, dedim, hatte, dachte, geldi, dediğim, geçti, dedi, başladım</em> * `Pqp` (48; 2% of non-empty `Tense`): <em>gitmiştik, gelmişti, gitmiştim, konuşmuştuk, yapmıştın, bakmıştım, başlamıştım, gitmişti, yapmıştım, Sormadıydım</em> * `Pres` (1875; 64% of non-empty `Tense`): <em>glaube, habe, oluyor, weiß, haben, weißt, gibt, bilmiyorum, denke, kommt</em> * `EMPTY` (1184): <em>machen, gemacht, gesagt, lernen, olarak, bak, angeschaut, gitmek, olsun, anfangen</em> <table> <tr><th>Paradigm <i>yap</i></th><th><tt>Pres</tt></th><th><tt>Fut</tt></th><th><tt>Past</tt></th><th><tt>Pqp</tt></th></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Hab</tt>|<tt><a href="qtd_sagt-feat-Case.html">Case</a></tt><tt>=Nom</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Fh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=GenPot</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt></tt></td><td><em>yapabiliriz</em></td><td></td><td></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Hab</tt>|<tt><a href="qtd_sagt-feat-Case.html">Case</a></tt><tt>=Nom</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Fh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Gen</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Number-psor.html">Number[psor]</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person-psor.html">Person[psor]</a></tt><tt>=1</tt></tt></td><td><em>yaparım</em></td><td></td><td></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Hab</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Fh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=GenPot</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=1</tt>|<tt><a href="qtd_sagt-feat-Polarity.html">Polarity</a></tt><tt>=Neg</tt></tt></td><td><em>yapamam</em></td><td></td><td></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Hab</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Fh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=GenPot</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=2</tt></tt></td><td><em>yapabilirsin</em></td><td></td><td></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Hab</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Fh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=GenPot</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=3</tt>|<tt><a href="qtd_sagt-feat-Voice.html">Voice</a></tt><tt>=Pass</tt></tt></td><td><em>yapılabilir</em></td><td></td><td></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Hab</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Fh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=GenPot</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Plur</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=1</tt></tt></td><td><em>yapabiliriz</em></td><td></td><td></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Hab</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Fh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=GenPot</tt>|<tt><a href="qtd_sagt-feat-Voice.html">Voice</a></tt><tt>=Pass</tt></tt></td><td><em>yapılabilir</em></td><td></td><td></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Hab</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Fh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Gen</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=1</tt></tt></td><td><em>yaparım</em></td><td></td><td></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Hab</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Fh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Gen</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=3</tt>|<tt><a href="qtd_sagt-feat-Polarity.html">Polarity</a></tt><tt>=Neg</tt></tt></td><td><em>yapmaz</em></td><td></td><td></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Hab</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Fh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Gen</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=3</tt>|<tt><a href="qtd_sagt-feat-VerbForm.html">VerbForm</a></tt><tt>=Conv</tt></tt></td><td><em>yaparken</em></td><td></td><td></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Hab</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Fh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Gen</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=3</tt>|<tt><a href="qtd_sagt-feat-VerbForm.html">VerbForm</a></tt><tt>=Conv</tt>|<tt><a href="qtd_sagt-feat-Voice.html">Voice</a></tt><tt>=Pass</tt></tt></td><td><em>yapılırken</em></td><td></td><td></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Hab</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Fh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Gen</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Plur</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=1</tt></tt></td><td><em>yaparız</em></td><td></td><td></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Hab</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Fh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Gen</tt>|<tt><a href="qtd_sagt-feat-VerbForm.html">VerbForm</a></tt><tt>=Conv</tt></tt></td><td><em>yaparken</em></td><td></td><td></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Hab</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Fh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Ind</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Plur</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=1</tt></tt></td><td></td><td></td><td><em>yapardık</em></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Hab</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Fh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Pot</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=1</tt></tt></td><td></td><td></td><td><em>yapabilirdim</em></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Imp</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Fh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Cnd</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=1</tt></tt></td><td><em>yaparsam</em></td><td></td><td></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Imp</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Fh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Cnd</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=2</tt></tt></td><td><em>yaparsan</em></td><td></td><td><em>yaptıysan</em></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Imp</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Fh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Cnd</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=3</tt></tt></td><td></td><td></td><td><em>yaptıysa</em></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Imp</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Fh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Des</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=3</tt>|<tt><a href="qtd_sagt-feat-Voice.html">Voice</a></tt><tt>=Pass</tt></tt></td><td><em>yapılırsa</em></td><td></td><td></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Imp</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Fh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Opt</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=1</tt></tt></td><td><em>yapayım</em></td><td></td><td></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Imp</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Fh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Opt</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Plur</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=1</tt></tt></td><td><em>yapalım</em></td><td></td><td></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Imp</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Nfh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Cnd</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=1</tt></tt></td><td><em>yapsam</em></td><td></td><td></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Imp</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Nfh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Des</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=2</tt></tt></td><td><em>yapsan</em></td><td></td><td></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Perf</tt>|<tt><a href="qtd_sagt-feat-Case.html">Case</a></tt><tt>=Acc</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Fh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Ind</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Number-psor.html">Number[psor]</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person-psor.html">Person[psor]</a></tt><tt>=1</tt></tt></td><td></td><td><em>yapacağımı</em></td><td></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Perf</tt>|<tt><a href="qtd_sagt-feat-Case.html">Case</a></tt><tt>=Nom</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Fh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Ind</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Number-psor.html">Number[psor]</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person-psor.html">Person[psor]</a></tt><tt>=1</tt></tt></td><td></td><td><em>yapacağım</em></td><td></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Perf</tt>|<tt><a href="qtd_sagt-feat-Case.html">Case</a></tt><tt>=Nom</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Nfh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Ind</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt></tt></td><td></td><td></td><td><em>yapmış</em></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Perf</tt>|<tt><a href="qtd_sagt-feat-Case.html">Case</a></tt><tt>=Nom</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Nfh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Ind</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Plur</tt></tt></td><td></td><td></td><td><em>yapmışlar</em></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Perf</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Fh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Cnd</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=2</tt></tt></td><td></td><td><em>yapacaksan</em></td><td></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Perf</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Fh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Ind</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=1</tt></tt></td><td></td><td><em>yapacağım</em></td><td><em>yaptım</em></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Perf</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Fh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Ind</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=1</tt>|<tt><a href="qtd_sagt-feat-Polarity.html">Polarity</a></tt><tt>=Neg</tt></tt></td><td></td><td></td><td><em>yapmadım</em></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Perf</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Fh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Ind</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=2</tt></tt></td><td></td><td><em>yapacaksın</em></td><td><em>yaptın</em></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Perf</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Fh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Ind</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=2</tt>|<tt><a href="qtd_sagt-feat-Polarity.html">Polarity</a></tt><tt>=Neg</tt></tt></td><td></td><td></td><td><em>yapmadın</em></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Perf</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Fh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Ind</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=3</tt></tt></td><td></td><td><em>yapacak</em></td><td><em>yaptı</em></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Perf</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Fh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Ind</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=3</tt>|<tt><a href="qtd_sagt-feat-Polarity.html">Polarity</a></tt><tt>=Neg</tt></tt></td><td></td><td></td><td><em>yapmadı</em></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Perf</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Fh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Ind</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=3</tt>|<tt><a href="qtd_sagt-feat-Voice.html">Voice</a></tt><tt>=Pass</tt></tt></td><td></td><td><em>yapılacak</em></td><td></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Perf</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Fh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Ind</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Plur</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=1</tt></tt></td><td></td><td><em>yapacağız</em></td><td><em>yaptık</em></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Perf</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Fh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Ind</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Plur</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=3</tt></tt></td><td></td><td><em>yapacaklar</em></td><td><em>yaptılar</em></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Perf</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Fh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Pot</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=1</tt>|<tt><a href="qtd_sagt-feat-Polarity.html">Polarity</a></tt><tt>=Neg</tt></tt></td><td></td><td></td><td><em>yapamadım</em></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Perf</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Fh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Pot</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=2</tt></tt></td><td></td><td></td><td><em>yapabildin</em></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Perf</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Nfh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Ind</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=1</tt></tt></td><td></td><td></td><td></td><td><em>yapmıştım</em></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Perf</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Nfh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Ind</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=2</tt></tt></td><td></td><td></td><td><em>yapmışsın</em></td><td><em>yapmıştın</em></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Perf</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Nfh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Ind</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=3</tt></tt></td><td></td><td></td><td><em>yapmış</em></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Perf</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Nfh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Ind</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Plur</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=3</tt></tt></td><td></td><td></td><td><em>yapmışlar</em></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Prog</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Fh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Cnd</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=2</tt></tt></td><td><em>yapıyorsan</em></td><td></td><td></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Prog</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Fh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Ind</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=1</tt></tt></td><td><em>yapıyorum</em></td><td></td><td></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Prog</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Fh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Ind</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=1</tt>|<tt><a href="qtd_sagt-feat-Polarity.html">Polarity</a></tt><tt>=Neg</tt></tt></td><td><em>yapmıyorum</em></td><td></td><td></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Prog</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Fh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Ind</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=2</tt></tt></td><td><em>yapıyorsun</em></td><td></td><td></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Prog</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Fh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Ind</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=2</tt>|<tt><a href="qtd_sagt-feat-Polarity.html">Polarity</a></tt><tt>=Neg</tt></tt></td><td><em>yapmıyorsun</em></td><td></td><td></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Prog</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Fh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Ind</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=3</tt></tt></td><td><em>yapıyor</em></td><td></td><td></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Prog</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Fh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Ind</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=3</tt>|<tt><a href="qtd_sagt-feat-Polarity.html">Polarity</a></tt><tt>=Neg</tt></tt></td><td><em>yapmıyor</em></td><td></td><td></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Prog</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Fh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Ind</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=3</tt>|<tt><a href="qtd_sagt-feat-Voice.html">Voice</a></tt><tt>=Pass</tt></tt></td><td><em>yapılıyor</em></td><td></td><td></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Prog</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Fh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Ind</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Plur</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=1</tt></tt></td><td><em>yapıyoruz</em></td><td></td><td></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Prog</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Fh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Ind</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Plur</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=3</tt></tt></td><td><em>yapıyorlar</em></td><td></td><td></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Prog</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Fh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Pot</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=1</tt></tt></td><td><em>yapabiliyorum</em></td><td></td><td></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Prog</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Fh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Pot</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=2</tt></tt></td><td><em>yapabiliyorsun</em></td><td></td><td></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Prog</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Nfh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Ind</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Plur</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=3</tt></tt></td><td><em>yapıyorlarmış</em></td><td></td><td></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=Prog</tt>|<tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=Nfh</tt>|<tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Ind</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Plur</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=3</tt>|<tt><a href="qtd_sagt-feat-Polarity.html">Polarity</a></tt><tt>=Neg</tt></tt></td><td><em>yapmıyorlarmış</em></td><td></td><td></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Case.html">Case</a></tt><tt>=Acc</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Number-psor.html">Number[psor]</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person-psor.html">Person[psor]</a></tt><tt>=1</tt>|<tt><a href="qtd_sagt-feat-VerbForm.html">VerbForm</a></tt><tt>=Part</tt></tt></td><td></td><td></td><td><em>yaptığımı</em></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Case.html">Case</a></tt><tt>=Acc</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Number-psor.html">Number[psor]</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person-psor.html">Person[psor]</a></tt><tt>=3</tt>|<tt><a href="qtd_sagt-feat-VerbForm.html">VerbForm</a></tt><tt>=Part</tt>|<tt><a href="qtd_sagt-feat-Voice.html">Voice</a></tt><tt>=Pass</tt></tt></td><td></td><td></td><td><em>yapıldığını</em></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Case.html">Case</a></tt><tt>=Loc</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Number-psor.html">Number[psor]</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person-psor.html">Person[psor]</a></tt><tt>=1</tt>|<tt><a href="qtd_sagt-feat-VerbForm.html">VerbForm</a></tt><tt>=Part</tt></tt></td><td></td><td></td><td><em>yaptığımda</em></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Case.html">Case</a></tt><tt>=Loc</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Number-psor.html">Number[psor]</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person-psor.html">Person[psor]</a></tt><tt>=3</tt>|<tt><a href="qtd_sagt-feat-VerbForm.html">VerbForm</a></tt><tt>=Part</tt></tt></td><td></td><td></td><td><em>yaptığında</em></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Case.html">Case</a></tt><tt>=Loc</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Number-psor.html">Number[psor]</a></tt><tt>=Plur</tt>|<tt><a href="qtd_sagt-feat-Person-psor.html">Person[psor]</a></tt><tt>=1</tt>|<tt><a href="qtd_sagt-feat-VerbForm.html">VerbForm</a></tt><tt>=Part</tt></tt></td><td></td><td></td><td><em>yaptığımızda</em></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Case.html">Case</a></tt><tt>=Nom</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Number-psor.html">Number[psor]</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person-psor.html">Person[psor]</a></tt><tt>=1</tt>|<tt><a href="qtd_sagt-feat-VerbForm.html">VerbForm</a></tt><tt>=Part</tt></tt></td><td></td><td><em>yapacağım</em></td><td><em>yaptığım</em></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Case.html">Case</a></tt><tt>=Nom</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Number-psor.html">Number[psor]</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person-psor.html">Person[psor]</a></tt><tt>=2</tt>|<tt><a href="qtd_sagt-feat-VerbForm.html">VerbForm</a></tt><tt>=Part</tt></tt></td><td></td><td></td><td><em>yaptığın</em></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Case.html">Case</a></tt><tt>=Nom</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Number-psor.html">Number[psor]</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person-psor.html">Person[psor]</a></tt><tt>=3</tt>|<tt><a href="qtd_sagt-feat-VerbForm.html">VerbForm</a></tt><tt>=Part</tt></tt></td><td></td><td></td><td><em>yaptığı</em></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Case.html">Case</a></tt><tt>=Nom</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Number-psor.html">Number[psor]</a></tt><tt>=Plur</tt>|<tt><a href="qtd_sagt-feat-Person-psor.html">Person[psor]</a></tt><tt>=1</tt>|<tt><a href="qtd_sagt-feat-VerbForm.html">VerbForm</a></tt><tt>=Part</tt></tt></td><td></td><td></td><td><em>yaptığımız</em></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Case.html">Case</a></tt><tt>=Nom</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Number-psor.html">Number[psor]</a></tt><tt>=Plur</tt>|<tt><a href="qtd_sagt-feat-Person-psor.html">Person[psor]</a></tt><tt>=2</tt>|<tt><a href="qtd_sagt-feat-VerbForm.html">VerbForm</a></tt><tt>=Part</tt></tt></td><td></td><td></td><td><em>yaptığınız</em></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Case.html">Case</a></tt><tt>=Nom</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Polarity.html">Polarity</a></tt><tt>=Neg</tt>|<tt><a href="qtd_sagt-feat-VerbForm.html">VerbForm</a></tt><tt>=Part</tt></tt></td><td></td><td></td><td><em>yapmadığ</em></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Case.html">Case</a></tt><tt>=Nom</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-VerbForm.html">VerbForm</a></tt><tt>=Part</tt></tt></td><td><em>yapan</em></td><td></td><td></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Ind</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=1</tt></tt></td><td></td><td></td><td><em>yaptım</em></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-VerbForm.html">VerbForm</a></tt><tt>=Part</tt>|<tt><a href="qtd_sagt-feat-Voice.html">Voice</a></tt><tt>=Pass</tt></tt></td><td><em>yapılan</em></td><td></td><td></td><td></td></tr> </table> ### `AUX` 1203 <tt><a href="qtd_sagt-pos-AUX.html">AUX</a></tt> tokens (85% of all `AUX` tokens) have a non-empty value of `Tense`. The most frequent other feature values with which `AUX` and `Tense` co-occurred: <tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Ind</tt> (1127; 94%), <tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt> (1059; 88%), <tt><a href="qtd_sagt-feat-Evident.html">Evident</a></tt><tt>=EMPTY</tt> (1055; 88%), <tt><a href="qtd_sagt-feat-Aspect.html">Aspect</a></tt><tt>=EMPTY</tt> (1054; 88%), <tt><a href="qtd_sagt-feat-VerbForm.html">VerbForm</a></tt><tt>=Fin</tt> (1022; 85%), <tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=3</tt> (668; 56%). `AUX` tokens may have the following values of `Tense`: * `Past` (364; 30% of non-empty `Tense`): <em>war, dı, würde, di, ydi, waren, wollte, hätte, wäre, ydı</em> * `Pres` (839; 70% of non-empty `Tense`): <em>ist, habe, hat, sind, muss, kann, haben, bin, kannst, musst</em> * `EMPTY` (206): <em>mi, mı, mu, sein, ken, musun, yim, ler, dır, yım</em> <table> <tr><th>Paradigm <i>sein</i></th><th><tt>Pres</tt></th><th><tt>Past</tt></th></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Ind</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=1</tt></tt></td><td><em>bin</em></td><td><em>war</em></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Ind</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=2</tt></tt></td><td><em>bist</em></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Ind</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=3</tt></tt></td><td><em>ist</em></td><td><em>war, waren</em></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Ind</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Plur</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=1</tt></tt></td><td><em>sind</em></td><td><em>waren</em></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Ind</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Plur</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=2</tt></tt></td><td><em>seid</em></td><td></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Ind</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Plur</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=3</tt></tt></td><td><em>sind, bin</em></td><td><em>waren</em></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Sub</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=1</tt></tt></td><td></td><td><em>wäre</em></td></tr> <tr><td><tt><tt><a href="qtd_sagt-feat-Mood.html">Mood</a></tt><tt>=Sub</tt>|<tt><a href="qtd_sagt-feat-Number.html">Number</a></tt><tt>=Sing</tt>|<tt><a href="qtd_sagt-feat-Person.html">Person</a></tt><tt>=3</tt></tt></td><td></td><td><em>wäre</em></td></tr> </table> ## Relations with Agreement in `Tense` The 10 most frequent relations where parent and child node agree in `Tense`: <tt>VERB --[<tt><a href="qtd_sagt-dep-conj.html">conj</a></tt>]--> VERB</tt> (262; 52%), <tt>VERB --[<tt><a href="qtd_sagt-dep-reparandum.html">reparandum</a></tt>]--> VERB</tt> (38; 73%), <tt>VERB --[<tt><a href="qtd_sagt-dep-dislocated.html">dislocated</a></tt>]--> VERB</tt> (7; 64%), <tt>AUX --[<tt><a href="qtd_sagt-dep-reparandum.html">reparandum</a></tt>]--> AUX</tt> (5; 71%), <tt>VERB --[<tt><a href="qtd_sagt-dep-compound-redup.html">compound:redup</a></tt>]--> VERB</tt> (5; 100%), <tt>VERB --[<tt><a href="qtd_sagt-dep-obl.html">obl</a></tt>]--> VERB</tt> (2; 67%), <tt>AUX --[<tt><a href="qtd_sagt-dep-parataxis-discourse.html">parataxis:discourse</a></tt>]--> VERB</tt> (1; 100%), <tt>VERB --[<tt><a href="qtd_sagt-dep-advcl.html">advcl</a></tt>]--> AUX</tt> (1; 100%), <tt>VERB --[<tt><a href="qtd_sagt-dep-obj.html">obj</a></tt>]--> VERB</tt> (1; 100%).

266.58042

582

0.624144

yue_Hant

0.688724

e96888895f8bd8ec04a00f1161c77ee03e41800f

3,601

md

Markdown

blog/2020-07-17-moku.md

hi120ki/isucon-cheatsheet

0e99ffdae22fbada27f4f163f1f5fa70862edefa

[ "MIT" ]

null

blog/2020-07-17-moku.md

hi120ki/isucon-cheatsheet

0e99ffdae22fbada27f4f163f1f5fa70862edefa

[ "MIT" ]

null

blog/2020-07-17-moku.md

hi120ki/isucon-cheatsheet

0e99ffdae22fbada27f4f163f1f5fa70862edefa

[ "MIT" ]

null

--- slug: 2020moku title: ISUCONもくもく会に参加しました author: hi120ki author_title: Team Wani author_url: https://github.com/hi120ki author_image_url: https://avatars1.githubusercontent.com/u/12624257 tags: [ISUCON, もくもく会] ---  ``` $ cd ~/minisucon2020/webapp/ruby $ bundle exec rackup ``` Ruby 製のマークダウンのメモ&コメントアプリケーションマニュアルをしっかり読む > 「ログを仕込む」を多用してひたすら計測 ### GitHub にレポジトリを作る ``` $ ssh-keygen -t ed25519 $ cat ~/.ssh/id_ed25519.pub ``` ``` $ cd ~/minisucon2020 $ git init $ git add . $ git commit -m "Init repository" $ git remote add origin git@github.com:hi120ki/minisucon2020.git $ git push -u origin master ``` > とりあえず全部アップする > > /etc/ファイルも保存したりしてる > > 運営から与えられた環境はきちんとバックアップする ### 重いところを見つけるトップページが明らかに重たいので改善する ``` $ MYSQL_QUERY_LOGGER=1 bundle exec rackup ``` SQL のログが出てくる > 本番では MYSQL_QUERY_LOGGER のような関数を自分で追加しないといけないのでスニペットを用意しておく > log の共有として gist をよく使うので慣れておく ### トップページでの表示件数を環境変数で減らす <https://github.com/hi120ki/minisucon2020/commit/2a4021348e54eba6955744ebae96a96a124f66dd> ``` $ ARTICLES_PER_PAGE=3 MYSQL_QUERY_LOGGER=1 bundle exec rackup ``` ### トップページにコメントの取得は必要ない <https://github.com/hi120ki/minisucon2020/commit/b77609a728aea238949fe14888f99cda9d556d16> **無駄なクエリを見つけよう！** ループの中で呼ばれるクエリを「N+1 Query」と呼ぶ別の関数として定義して変更を加えてコンフリクトを防止する ### コメント取得の改善 ``` [SQL] (7ms) SELECT COUNT(*) as `count` FROM `comments` WHERE `article_id` = '800' AND `user_id` NOT IN ('2','3','4','5','6','7','8') ORDER BY `id` DESC, `user_id` ASC ``` 7ms は遅い ``` $ mysql -u root $ use `minisucon2020`; mysql> EXPLAIN SELECT COUNT(*) as `count` FROM `comments` WHERE `article_id` = '800' AND `user_id` NOT IN ('2','3','4','5','6','7','8') ORDER BY `id` DESC, `user_id` ASC; +----+-------------+----------+------------+------+---------------+------+---------+------+-------+----------+-------------+ | id | select_type | table | partitions | type | possible_keys | key | key_len | ref | rows | filtered | Extra | +----+-------------+----------+------------+------+---------------+------+---------+------+-------+----------+-------------+ | 1 | SIMPLE | comments | NULL | ALL | NULL | NULL | NULL | NULL | 22780 | 5.00 | Using where | +----+-------------+----------+------------+------+---------------+------+---------+------+-------+----------+-------------+ ``` 「type all」全件検索「possible_keys NULL」インデックスなし「rows」22780 件から「filtered」5%しか取ってきていないインデックスを追加する ``` INDEX idx_count (`article_id`, `user_id`) ``` <https://github.com/hi120ki/minisucon2020/commit/3c4762c7acbce70ba8f9a82848ccc5f0137ac920> > SQL の実行計画(EXPLAIN SELECT ~)を見て rows filter extra をチェックする ### 記事取得の取得 ``` mysql> EXPLAIN SELECT * FROM `articles` WHERE `user_id` NOT IN ('0') ORDER BY `id` DESC LIMIT 4 OFFSET 0; ``` type ALL filtered 90 <https://github.com/hi120ki/minisucon2020/commit/132580d6d97bff9377be0d9b9a85ee150a4a5c0e> <https://github.com/hi120ki/minisucon2020/commit/2a92d6888ca2f917604e0d5e124c55331f157356> type index になる > EXPLAIN で調査から index を貼ることは大事 > > 基本的には where 文の条件キーを加えていく ### 不変なクエリ結果をメモリにキャッシュしてみる get_user の結果をキャッシュする複数台なら redis <https://github.com/hi120ki/minisucon2020/commit/1e73dea0f1db9fa115df7c92e09c3454063759a7> ## user icon の改善 <https://github.com/hi120ki/minisucon2020/commit/6d1ac93bad835a1b9b4378d1d0ed1bbab9a4f4e3> ``` $ sudo cp ~/minisucon2020/nginx.conf /etc/nginx/nginx.conf $ sudo service nginx restart ``` ## user icon を静的ファイル化 <https://github.com/hi120ki/minisucon2020/commit/e6759df96fb252546503b237f92a9afcd6f62265> /initialize リクエストが飛ぶと静的ファイルが生成される ## 大切なことアプリケーションを壊さない再起動試験に耐える小さなことからこつこつと

21.824242

170

0.656207

yue_Hant

0.580948

e968c3a7a731bb769d45a4da814453a0f3f7d833

15

md

Markdown

README.md

filchyboy/AcmeLabs

9eb67ec0ecabe1101f944fac848c4b6a146276ea

[ "MIT" ]

null

README.md

filchyboy/AcmeLabs

9eb67ec0ecabe1101f944fac848c4b6a146276ea

[ "MIT" ]

null

README.md

filchyboy/AcmeLabs

9eb67ec0ecabe1101f944fac848c4b6a146276ea

[ "MIT" ]

null

# AcmeLabs DS

5

10

0.666667

kor_Hang

0.383535

e9692f3c9856520a17f6822d1010187b8ae3964d

2,258

md

Markdown

docs/handlers/direct_handler.md

peter279k/SnappyRouter

8565170212db56e0f9c5a77fb08bf54e8caeb4cc

[ "MIT" ]

null

docs/handlers/direct_handler.md

peter279k/SnappyRouter

8565170212db56e0f9c5a77fb08bf54e8caeb4cc

[ "MIT" ]

null

docs/handlers/direct_handler.md

peter279k/SnappyRouter

8565170212db56e0f9c5a77fb08bf54e8caeb4cc

[ "MIT" ]

null

# Direct Script Handler The direct script handler maps web requests to raw PHP scripts. For PHP applications that do not use the front controller pattern and do not have a single entry point, this handler can be used to provide one without affecting any of the current code. ## How to use it The handler works by scanning the path for a specific prefix and matching it to a locally stored folder. For example we may have a folder structure like: ``` /home/user/ webroot/ index.html scripts/ test_script.php ``` with our web server configured to use `/home/user/webroot` as the default document root. Accessing the script directly would be done through a url like: ``` http://localhost/scripts/test_script.php ``` The handler can then be configured as such: ```php <?php use Vectorface\SnappyRouter\Config\Config; use Vectorface\SnappyRouter\Handler\DirectScriptHandler; $config = new Config(array( Config::KEY_HANDLERS => array( 'DirectHandler' => array( Config::KEY_CLASS => 'Vectorface\\SnappyRouter\\Handlers\\DirectScriptHandler', Config::KEY_OPTIONS => array( DirectScriptHandler::KEY_PATH_MAP => array( '/scripts/' => '/home/user/webroot/scripts', '/' => '/home/user/webroot/scripts' ) ), Config::KEY_PLUGINS => array( // optional list of plugins to put in front of your scripts ) ) ) )); $router = new Vectorface\SnappyRouter\SnappyRouter($config); echo $router->handleRoute(); ``` ## Path Map Fallback Strategy Many application environments use virtual hosts, path aliases, symbolic links, etc. The URL to a particular script may not always be obvious and consistent across production, test, and local development environments. For this reason, the `DirectScriptHandler::KEY_PATH_MAP` config option supports multiple path prefixes which the handler will try each one iteratively (in order) until it finds a matching script. In the above example, we may have a virtual host pointing directly to the scripts folder, and the above configuration would continue to work. For example: ``` http://livesite.example.com/test_script.php ```

30.931507

91

0.70062

eng_Latn

0.966879

e969546826a7b9bfbab02ccc18ee2cf8a6d79358

16,777

md

Markdown

articles/databox-online/data-box-gateway-deploy-provision-vmware.md

eltociear/azure-docs.de-de

7171dffd9fa27c72cc17bb1916941cb64330a2af

[ "CC-BY-4.0", "MIT" ]

1

2020-04-03T08:58:02.000Z

articles/databox-online/data-box-gateway-deploy-provision-vmware.md

eltociear/azure-docs.de-de

7171dffd9fa27c72cc17bb1916941cb64330a2af

[ "CC-BY-4.0", "MIT" ]

null

articles/databox-online/data-box-gateway-deploy-provision-vmware.md

eltociear/azure-docs.de-de

7171dffd9fa27c72cc17bb1916941cb64330a2af

[ "CC-BY-4.0", "MIT" ]

null

--- title: Tutorial zum Bereitstellen von Azure Data Box Gateway in VMware | Microsoft-Dokumentation description: Im zweiten Tutorial zum Bereitstellen von Azure Data Box Gateway geht es um die Bereitstellung eines virtuellen Geräts in VMware. services: databox author: alkohli ms.service: databox ms.subservice: gateway ms.topic: tutorial ms.date: 03/25/2019 ms.author: alkohli ms.openlocfilehash: 85992224edd10c0a0f233de9f6274cc77e109b22 ms.sourcegitcommit: 0947111b263015136bca0e6ec5a8c570b3f700ff ms.translationtype: HT ms.contentlocale: de-DE ms.lasthandoff: 03/24/2020 ms.locfileid: "60757556" --- # <a name="tutorial-provision-azure-data-box-gateway-in-vmware"></a>Tutorial: Bereitstellen von Azure Data Box Gateway in VMware ## <a name="overview"></a>Übersicht In diesem Tutorial wird beschrieben, wie Sie Data Box Gateway auf einem Hostsystem mit VMware ESXi 6.0, 6.5 oder 6.7 bereitstellen. Sie benötigen Administratorrechte, um ein virtuelles Gerät bereitzustellen und zu verbinden. Die Bereitstellung und die anfängliche Einrichtung dauern ca. 10 Minuten. In diesem Tutorial lernen Sie Folgendes: > [!div class="checklist"] > * Sicherstellen, dass der Host die Mindestanforderungen für Geräte erfüllt > * Bereitstellen eines virtuellen Geräts in VMware > * Starten des virtuellen Geräts und Abrufen der IP-Adresse Wenn Sie kein Azure-Abonnement besitzen, können Sie ein [kostenloses Konto](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) erstellen, bevor Sie beginnen. ## <a name="prerequisites"></a>Voraussetzungen Für die Bereitstellung eines virtuellen Geräts auf einem Hostsystem mit VMware ESXi 6.0, 6.5 oder 6.7 gelten die folgenden Voraussetzungen. ### <a name="for-the-data-box-gateway-resource"></a>Für die Data Box Gateway-Ressource Stellen Sie Folgendes sicher, bevor Sie beginnen: * Sie haben alle Schritte unter [Vorbereiten des Portals für Data Box Gateway](data-box-gateway-deploy-prep.md) ausgeführt. * Sie haben das Image des virtuellen Geräts für VMware wie unter [Vorbereiten des Portals für Data Box Gateway](data-box-gateway-deploy-prep.md) beschrieben aus dem Azure-Portal heruntergeladen. > [!IMPORTANT] > Die auf dem Data Box Gateway ausgeführte Software kann nur mit der Data Box Gateway-Ressource verwendet werden. ### <a name="for-the-data-box-gateway-virtual-device"></a>Für das virtuelle Data Box Gateway-Gerät Stellen Sie Folgendes sicher, bevor Sie ein virtuelles Gerät bereitstellen: * Sie haben Zugriff auf ein Hostsystem mit VMware (ESXi 6.0, 6.5 oder 6.7), das zum Bereitstellen eines Geräts verwendet werden kann. * Das Hostsystem verfügt für die Bereitstellung des virtuellen Geräts über die folgenden Ressourcen: * Mindestens 4 Kerne * Mindestens 8 GB RAM * Eine Netzwerkschnittstelle * Einen Betriebssystemdatenträger mit 250 GB * Einen virtuellen Datenträger mit 2 TB für Systemdaten ### <a name="for-the-network-in-datacenter"></a>Für das Netzwerk im Rechenzentrum Vorbereitungen - Lesen Sie die Netzwerkanforderungen für die Bereitstellung eines Data Box Gateway, und konfigurieren Sie das Netzwerk des Datencenters gemäß den Anforderungen. Weitere Informationen finden Sie unter [Data Box Gateway – Netzwerkanforderungen](data-box-gateway-system-requirements.md#networking-port-requirements). - Stellen Sie sicher, dass die Internetbandbreite mindestens 20 MBit/s beträgt, um die optimale Nutzung des Geräts zu ermöglichen. ## <a name="check-the-host-system"></a>Überprüfen des Hostsystems Zum Erstellen eines virtuellen Geräts benötigen Sie Folgendes: * Zugriff auf ein Hostsystem mit VMware ESXi Server 6.0, 6.5 oder 6.7. Das Hostsystem muss die folgenden Ressourcen für Ihr virtuelles Gerät reservieren können: * Mindestens vier virtuelle Prozessoren * Mindestens 8 GB RAM * Eine mit dem Netzwerk verbundene Netzwerkschnittstelle, über die Datenverkehr ins Internet weitergeleitet werden kann. * Einen Betriebssystemdatenträger mit 250 GB * Einen virtuellen Datenträger mit 2 TB für Daten * VMware vSphere-Client auf Ihrem System zum Verwalten des ESXi-Hosts ## <a name="provision-a-virtual-device-in-hypervisor"></a>Bereitstellen eines virtuellen Geräts in VMware Führen Sie die folgenden Schritte aus, um ein virtuelles Gerät in VMware bereitzustellen. 1. Kopieren Sie das Image mit dem virtuellen Gerät auf Ihr System. Dies ist das virtuelle Image (zwei Dateien), das Sie über das Azure-Portal heruntergeladen haben. Notieren Sie sich den Speicherort, an den Sie das Image kopiert haben, da Sie es später noch benötigen. 2. Melden Sie sich über einen Browser unter der folgenden URL beim ESXi-Server an: `https://<IP address of the ESXi server>`. Sie benötigen Administratorrechte, um einen virtuellen Computer zu erstellen. ![Anmeldeseite](./media/data-box-gateway-deploy-provision-vmware/image1.png) 3. Laden Sie das VMDK auf den ESXi-Server hoch. Klicken Sie im Navigatorbereich auf **Storage** (Speicher). ![](./media/data-box-gateway-deploy-provision-vmware/image2.png) 4. Wählen Sie im rechten Bereich unter **Datenspeicher**den Datenspeicher aus, in den Sie das VMDK hochladen möchten. - Der Datenspeicher muss vom Typ VMFS5 sein. - Der Datenspeicher muss zudem über genügend freien Speicherplatz für die Datenträger für das Betriebssystem und die Daten verfügen. 5. Klicken Sie mit der rechten Maustaste, und wählen Sie **Datenspeicher durchsuchen** aus. ![Durchsuchen des Datenspeichers](./media/data-box-gateway-deploy-provision-vmware/image3.png) 6. Das Fenster **Datenspeicher-Browser** wird angezeigt. ![Datenspeicher-Browser](./media/data-box-gateway-deploy-provision-vmware/image4.png) 7. Klicken Sie auf der Symbolleiste auf **Create directory** (Verzeichnis erstellen), um einen neuen Ordner zu erstellen. Geben Sie den Ordnernamen an, und notieren Sie ihn sich. Sie verwenden diesen Ordnernamen später beim Erstellen einer virtuellen Maschine (empfohlene bewährte Methode). Klicken Sie auf **Create directory** (Verzeichnis erstellen). ![Erstellen eines Verzeichnisses](./media/data-box-gateway-deploy-provision-vmware/image5.png) 8. Der neue Ordner wird im linken Bereich des **Datenspeicher-Browsers** angezeigt. Klicken Sie auf das Symbol **Upload**, und wählen Sie **Upload File** (Datei hochladen) aus. ![Hochladen der Datei](./media/data-box-gateway-deploy-provision-vmware/image6.png) 9. Rufen Sie das Verzeichnis auf, in das Sie die VMDK-Dateien heruntergeladen haben. Es enthält zwei Dateien. Wählen Sie die Datei aus, die Sie hochladen wollen. ![Auswählen der hochzuladenden Datei](./media/data-box-gateway-deploy-provision-vmware/image7.png) 10. Klicken Sie auf **Öffnen**. Der Upload der VMDK-Datei in den angegebenen Datenspeicher wird gestartet. Das Hochladen der Datei kann mehrere Minuten dauern. 11. Sobald der Upload abgeschlossen ist, können Sie die Datei im Datenspeicher in dem von Ihnen erstellten Ordner sehen. Laden Sie nun die zweite VMDK-Datei in den gleichen Datenspeicher hoch. Nachdem die beiden Dateien hochgeladen wurden, werden sie in einer einzelnen Datei zusammengeführt. Sie sehen dann nur eine Datei im Verzeichnis. ![Zwei VMDK-Dateien werden in einer einzelnen Datei zusammengeführt.](./media/data-box-gateway-deploy-provision-vmware/image8.png) 12. Wechseln Sie zurück zum vSphere-Clientfenster. Klicken Sie im Navigatorbereich auf **Virtual Machines** (VMs). Klicken Sie im rechten Bereich auf **Create/Register VM** (VM erstellen/registrieren). ![Erstellen oder Registrieren eines virtuellen Computers](./media/data-box-gateway-deploy-provision-vmware/image9.png) 13. Ein Fenster **New Virtual Machine** (Neue VM) wird angezeigt. Wählen Sie unter „Select creation type“ (Erstellungstyp auswählen) die Option **Create a new virtual machine** (Neue VM erstellen) aus, und klicken Sie auf **Next** (Weiter). ![Seite zum Auswählen des Erstellungstyps](./media/data-box-gateway-deploy-provision-vmware/image10.png) 14. Geben Sie auf der Seite **Select a name and guest OS** (Namen und Gastbetriebssystem auswählen) den **Namen** Ihrer VM an. Dieser Name sollte mit dem Ordnernamen übereinstimmen, den Sie in Schritt 7 angegeben haben (empfohlene bewährte Methode). Wählen Sie für **Guest OS family** (Gastbetriebssystemfamilie) Windows und für **Guest OS version** (Gastbetriebssystemversion) Microsoft Windows Server 2016 (64-Bit) aus. Klicken Sie auf **Weiter**. ![Seite zum Auswählen eines Namens, eines Betriebssystems und eines Speicherorts](./media/data-box-gateway-deploy-provision-vmware/image11.png) 15. Wählen Sie auf der Seite **Select storage** (Speicher auswählen) einen Datenspeicher aus, den Sie zum Bereitstellen der VM verwenden möchten. Klicken Sie auf **Weiter**. ![Seite zum Auswählen des Speichers](./media/data-box-gateway-deploy-provision-vmware/image12.png) 16. Legen Sie auf der Seite **Customize settings** (Einstellungen anpassen) **CPU** auf 4, **Memory** (Arbeitsspeicher) auf 8.192 MB (oder mehr) und **Hard disk 1** (Festplatte 1) auf 2 TB (oder mehr) fest. Wählen Sie die **SCSI-Festplatte** aus, die Sie hinzufügen möchten. In diesem Fall wurde „LSI Logic SAS“ ausgewählt. **Statische IDE-Datenträger werden nicht unterstützt.** **Hard disk 1** (Festplatte 1) ist der virtuelle Datenträger. Beachten Sie, dass Sie den Datenträger nach der Bereitstellung nicht mehr verkleinern können. Der Versuch, den Datenträger zu verkleinern, führt zum Verlust aller lokalen Daten auf dem Gerät. ![Seite zum Anpassen von Einstellungen](./media/data-box-gateway-deploy-provision-vmware/image13.png) Klicken Sie auf der gleichen Seite auf **Add hard disk** (Festplatte hinzufügen), und wählen Sie dann **Existing hard disk** (Vorhandene Festplatte) aus. Wählen Sie die VMDK-Datei im Datenspeicher aus. Dadurch wird ein Betriebssystemdatenträger hinzugefügt. Seite zum Anpassen von Einstellungen[](./media/data-box-gateway-deploy-provision-vmware/image14.png) Scrollen Sie nach unten, bis Sie den Eintrag **New hard disk** (Neue Festplatte) sehen, und erweitern Sie ihn, um die Einstellungen anzuzeigen. Legen Sie **Virtual Device Node** (Virtueller Geräteknoten) auf **IDE controller 0** (IDE-Controller 0) fest. ![Seite zum Anpassen von Einstellungen](./media/data-box-gateway-deploy-provision-vmware/image15.png) 17. *(Optional: Führen Sie diesen Schritt nur aus, wenn Sie VMware ESXi Server 6.7 verwenden.)* Klicken Sie auf der Seite **Customize settings** (Einstellungen anpassen) auf **VM options** (VM-Optionen). Navigieren Sie zu **Boot options > Firmware** (Startoptionen > Firmware), und ändern Sie die Option in **BIOS**. Standardmäßig ist der Wert auf „EFI“ festgelegt. Klicken Sie auf **Weiter**. ![Seite zum Anpassen von Einstellungen, wenn VMware ESXi Server 6.7 ausgeführt wird](./media/data-box-gateway-deploy-provision-vmware/image15a.png) 18. Prüfen Sie auf der Seite **Für Fertigstellung bereit** alle Einstellungen, die der neuen virtuellen Maschine zugeordnet sind. Vergewissern Sie sich, dass für die CPU 4, für den Arbeitsspeicher 8.192 MB, für die Netzwerkschnittstelle 1 und für Festplatte 2 der IDE-Controller 0 angezeigt werden. Klicken Sie auf **Fertig stellen**. ![Seite „Zum Abschluss bereit“](./media/data-box-gateway-deploy-provision-vmware/image16.png) ![Seite „Zum Abschluss bereit“](./media/data-box-gateway-deploy-provision-vmware/image17.png) Ihre virtuelle Maschine wird nun bereitgestellt. Es wird eine Benachrichtigung mit dem Hinweis angezeigt, dass die neue VM der Liste der VMs hinzugefügt wird. ![Neuer virtueller Computer zur Liste der VMs hinzugefügt](./media/data-box-gateway-deploy-provision-vmware/image17.png) Im nächsten Schritt wird der virtuelle Computer eingeschaltet und die IP-Adresse abgerufen. > [!NOTE] > Wir empfehlen, keine VMware-Tools auf dem virtuellen Gerät zu installieren (wie oben beschrieben wird). Die Installation von VMware-Tools führt zu einer nicht unterstützten Konfiguration. ## <a name="start-the-virtual-device-and-get-the-ip"></a>Starten des virtuellen Geräts und Abrufen der IP-Adresse Führen Sie die folgenden Schritte aus, um Ihr virtuelles Gerät zu starten und eine Verbindung dafür herzustellen. #### <a name="to-start-the-virtual-device"></a>So starten Sie das virtuelle Gerät 1. Starten Sie das virtuelle Gerät. Wählen Sie im rechten Bereich Ihr Gerät in der Liste der VMs aus, und klicken Sie mit der rechten Maustaste, um das Kontextmenü anzuzeigen. Wählen Sie **Ein/Aus** und dann **Einschalten**. Die virtuelle Maschine sollte nun eingeschaltet werden. Der Status wird im unteren Bereich des Webclients angezeigt. ![Einschalten des virtuellen Geräts](./media/data-box-gateway-deploy-provision-vmware/image19.png) 2. Wählen Sie erneut Ihre VM aus. Klicken Sie mit der rechten Maustaste, wählen Sie **Console** (Konsole) und dann **Open in a new window** (In einem neuen Fenster öffnen) aus. ![Öffnen der Konsole des virtuellen Geräts](./media/data-box-gateway-deploy-provision-vmware/image20.png) 3. Die Konsole der VM wird in einem neuen Fenster geöffnet. ![Konsole des virtuellen Geräts](./media/data-box-gateway-deploy-provision-vmware/image21.png) 4. Sobald das Gerät ausgeführt wird, klicken Sie auf die Registerkarte oben im mittleren Bereich des Konsolenfensters. Klicken Sie auf **Guest OS > Send keys > Ctrl+Alt+Delete** (Gastbetriebssystem > Tasteneingaben senden > STRG+ALT+ENTF). Hierdurch wird die VM entsperrt. ![Entsperren des virtuellen Geräts](./media/data-box-gateway-deploy-provision-vmware/image22.png) 5. Geben Sie das Kennwort ein, um sich bei der VM anzumelden. Das Standardkennwort lautet *Password1*. ![Eingeben eines Kennworts für das virtuelle Gerät](./media/data-box-gateway-deploy-provision-vmware/image23.png) 6. Die Schritte 5 bis 7 gelten nur beim Starten in anderen Umgebungen als einer DHCP-Umgebung. Wenn Sie in einer DHCP-Umgebung arbeiten, überspringen Sie diese Schritte, und fahren Sie mit Schritt 8 fort. Wenn Sie Ihr Gerät in einer anderen Umgebung als einer DHCP-Umgebung gestartet haben, wird eine entsprechende Meldung angezeigt: **Verwenden Sie das Cmdlet „Set-HcsIPAddress“, um das Netzwerk zu konfigurieren**. 7. Führen Sie zum Konfigurieren des Netzwerks an der Eingabeaufforderung den Befehl `Get-HcsIpAddress` aus, um die Netzwerkschnittstellen aufzulisten, die auf dem virtuellen Gerät aktiviert sind. Wenn für das Gerät eine einzelne Netzwerkschnittstelle aktiviert ist, wird dieser Schnittstelle der Standardname `Ethernet`zugewiesen. 8. Verwenden Sie das `Set-HcsIpAddress` -Cmdlet, um das Netzwerk zu konfigurieren. Unten ist ein Beispiel angegeben: `Set-HcsIpAddress –Name Ethernet –IpAddress 10.161.22.90 –Netmask 255.255.255.0 –Gateway 10.161.22.1` 9. Nachdem die anfängliche Einrichtung abgeschlossen und das Gerät gestartet wurde, wird der Bannertext für das Gerät angezeigt. Notieren Sie sich die IP-Adresse und die URL, die im Bannertext für die Verwaltung des Geräts angezeigt wird. Sie verwenden diese IP-Adresse zum Herstellen der Verbindung mit der Webbenutzeroberfläche Ihres virtuellen Geräts und zum Durchführen des lokalen Setups und der Aktivierung. ![Bannertext und Verbindungs-URL für das virtuelle Gerät](./media/data-box-gateway-deploy-provision-vmware/image24.png) Wenn Ihr Gerät die Mindestanforderungen für die Konfiguration nicht erfüllt, wird im Bannertext ein Fehler angezeigt (siehe unten). Sie müssen die Gerätekonfiguration ändern, damit sie über ausreichende Ressourcen zum Erfüllen der Mindestanforderungen verfügt. Sie können das Gerät dann neu starten und die Verbindung dafür herstellen. Die Mindestanforderungen für die Konfiguration finden Sie unter [Überprüfen des Hostsystems](#check-the-host-system). Falls bei der anfänglichen Konfiguration über die lokale Webbenutzeroberfläche andere Fehler auftreten, finden Sie weitere Informationen in den folgenden Workflows: - [Ausführen von Diagnosetests zum Beheben von Setup-Fehlern für die Web-UI](data-box-gateway-troubleshoot.md#run-diagnostics) - [Generieren des Protokollpakets und Anzeigen von Protokolldateien](data-box-gateway-troubleshoot.md#collect-support-package) ## <a name="next-steps"></a>Nächste Schritte In diesem Tutorial haben Sie sich mit den folgenden Themen zu Data Box Gateway befasst: > [!div class="checklist"] > * Sicherstellen, dass der Host die Mindestanforderungen für Geräte erfüllt > * Bereitstellen eines virtuellen Geräts in VMware > * Starten des virtuellen Geräts und Abrufen der IP-Adresse Im nächsten Tutorial erfahren Sie, wie Sie Ihr virtuelles Gerät verbinden, einrichten und aktivieren. * [Einrichten und Herstellen einer Verbindung mit Freigaben auf dem Data Box Gateway](data-box-gateway-deploy-connect-setup-activate.md)

73.262009

634

0.78852

deu_Latn

0.995826

e96a54c161d99516b8b3193561e2c7623578f711

939

markdown

Markdown

2012/guadec-second-round-for-me.markdown

aperezdc/perezdecastro.org

dcdba68490c34c5930a26c40c23f6e0fae367fa2

[ "MIT" ]

6

2015-06-24T20:03:37.000Z

2021-04-26T20:26:18.000Z

2012/guadec-second-round-for-me.markdown

aperezdc/perezdecastro.org

dcdba68490c34c5930a26c40c23f6e0fae367fa2

[ "MIT" ]

4

2015-12-30T16:48:31.000Z

2019-10-02T14:44:08.000Z

2012/guadec-second-round-for-me.markdown

aperezdc/perezdecastro.org

dcdba68490c34c5930a26c40c23f6e0fae367fa2

[ "MIT" ]

9

2015-03-09T04:15:27.000Z

2021-08-19T20:45:13.000Z

Title: GUADEC, second round (for me) Date: 2012-07-23 16:48 Author: aperez Tags: conferences, gnome, igalia Last summer I had the opportunity of attending the [Desktop Summit][] in Berlin, and being it a great experience I was more than looking forward to attend [GUADEC][] this year. Not just because it is going to be great to meet fellow hackers and friends after one year and attend the sessions, but also because it is taking place in A Coruña, where I lived for a decade. Last, but not least, there will be a GNOME OS hackfest on July 30th (check it out in the [BoF/hackfests programme][]) and lately that has been something which [has been in my list of interests][]. See you there! [Desktop Summit]: https://www.desktopsummit.org/ [GUADEC]: http://2012.guadec.org/ [BoF/hackfests programme]: https://live.gnome.org/GUADEC/2012/BOFs [has been in my list of interests]: /aperez/2012/06/15/the-gnome-the-os-and-the-ostree/

44.714286

89

0.751864

eng_Latn

0.996637

e96abfbe5b420e4f5a5c5e37ef03908ea3468e3d

619

md

Markdown

README.md

hyiso/vue-simple-datepicker

eb72257c2fe3105991d32c296a77888d14aefc00

[ "MIT" ]

8

2016-07-12T21:13:11.000Z

2020-02-14T07:29:51.000Z

README.md

hyiso/vue-simple-datepicker

eb72257c2fe3105991d32c296a77888d14aefc00

[ "MIT" ]

1

2016-10-11T08:25:48.000Z

2016-10-12T16:20:18.000Z

README.md

hyiso/vue-simple-datepicker

eb72257c2fe3105991d32c296a77888d14aefc00

[ "MIT" ]

4

2017-03-20T07:29:50.000Z

2018-08-17T21:50:58.000Z

# vue-simple-datepicker a simple datepicker component based on vue # Test ``` npm install . npm run test ``` # Usage ``` npm install vue-simple-datepicker ``` In your *.html page,use: ``` <body> <simple-datepicker :value.sync="today" format="YYYY/MM/DD"></simple-datepicker> <p>date picked: {{today}}</p> </body> ``` In your app.js,use it like the: ``` import simpleDatepicker from 'vue-simple-datepicker' new Vue({ el: 'body', data () { return { today: '2016/04/26' } }, components: { 'simple-datepicker': simpleDatepicker } }) ``` # License MIT

16.289474

52

0.597738

eng_Latn

0.526574

e96ac45ae8b49dd6f7b70b2c42ac92155b792b70

7,945

md

Markdown

docs/src/stimulus.md

haberdashPI/TimedPlayback.jl

759f757d6f79e498144e53daf846aba05291a0a1

[ "MIT" ]

null

docs/src/stimulus.md

haberdashPI/TimedPlayback.jl

759f757d6f79e498144e53daf846aba05291a0a1

[ "MIT" ]

null

docs/src/stimulus.md

haberdashPI/TimedPlayback.jl

759f757d6f79e498144e53daf846aba05291a0a1

[ "MIT" ]

1

2020-02-08T11:49:43.000Z

# How to create sounds There are two primary ways to create sounds: loading a file and composing sound primitives. ## Loading a file You can play or create sounds from files by directly playing the filename, or creating a sound first ```julia play("mysound_file.wav") x = sound("mysound_file.wav") play(x) ``` If you need to manipulate the sound before playing it, you can load it using [`sound`](@ref). For example, to remove any frequencies from `"mysound.wav"` above 400Hz before playing the sound, you could do the following. ```julia mysound = lowpass(sound("mysound.wav"),400Hz) play(mysound) ``` ## Sound Primitives There are several primitives you can use to generate simple sounds. They are [`tone`](@ref) (to create a pure), [`noise`](@ref) (to generate white noise), [`silence`](@ref) (for a silent period) and [`harmonic_complex`](@ref) (to create multiple pure tones with integer frequency ratios). These primitives can then be combined and manipulated to generate more interesting sounds. You can filter sounds ([`bandpass`](@ref), [`bandstop`](@ref), [`lowpass`](@ref), [`highpass`](@ref) and [`lowpass`](@ref)), mix them together ([`mix`](@ref)) and set an appropriate decibel level ([`attenuate`](@ref)). You can also manipulate the envelope of the sound ([`ramp`](@ref), [`rampon`](@ref), [`rampoff`](@ref), [`fadeto`](@ref), [`envelope`](@ref) and [`mult`](@ref)). For instance, to play a 1 kHz tone for 1 second inside of a noise with a notch from 0.5 to 1.5 kHz, with 5 dB SNR you could call the following. ```julia mysound = tone(1kHz,1s) mysound = ramp(mysound) mysound = attenuate(mysound,20) mynoise = noise(1s) mynoise = bandstop(mynoise,0.5kHz,1.5kHz) mynoise = attenuate(mynoise,25) play(mix(mysound,mynoise)) ``` TimedSound exports the macro `@>` (from [Lazy.jl](https://github.com/MikeInnes/Lazy.jl#macros)) to simplify this pattern. It is easiest to understand the macro by example: the below code yields the same result as the code above. ```juila mytone = @> tone(1kHz,1s) ramp attenuate(20) mynoise = @> noise(1s) bandstop(0.5kHz,1.5kHz) attenuate(25) play(mix(mytone,mynoise)) ``` TimedSound also exports `@>>`, and `@_` (refer to [Lazy.jl](https://github.com/MikeInnes/Lazy.jl#macros) for details). ### Sounds are arrays Sounds are just a specific kind of array of real numbers. The amplitudes of a sound are represented as real numbers between -1 and 1 in sequence at a sampling rate specific to the sound's type. They can be manipulated in the same way that any array can be manipulated in Julia, with some additional support for indexing sounds using time units. For instance, to get the first 5 seconds of a sound you can do the following. ```julia mytone = tone(1kHz,10s) mytone[0s .. 5s] ``` To represent the end of a sound using this special indexing, you can use `ends`. For instance, to get the last 5 seconds of `mysound` you can do the following. ```julia mytone[5s .. ends] ``` We can concatenate multiple sounds, to play them in sequence. The following code plays two tones in sequence, with a 100 ms gap between them. ```julia interval = [tone(400Hz,50ms); silence(100ms); tone(400Hz * 2^(5/12),50ms)] play(interval) ``` ### Sounds as normal arrays To represent a sound as a standard array (without copying any data), you may call the `Array` constructor. ```julia a = Array(mysound) ``` ### Stereo Sounds You can create stereo sounds with [`leftright`](@ref), and reference the left and right channel using `:left` or `:right` as a second index, like so. ```julia stereo_sound = leftright(tone(1kHz,2s),tone(2kHz,2s)) play(stereo_sound[:,:left]) play(stereo_sound[:,:right]) ``` The functions [`left`](@ref) and [`right`](@ref) can also extract the left and right channel, but work on both sounds and streams. # Timing Sounds A key fature of TimedSounds is that you can time the presentation of the sounds. This is done using the `at` function to get a specific time stamp and the `time` keyword argument to `play`, as follows. ```julia using TimedSound reference = at(1s) # 1 second from now sound1_time = reference sound2_time = reference + 200ms sound3_time = reference + 2s sound1 = @> tone(1kHz) attenuate(20) # an unending 1 kHz pure tone sound2 = @> sound("mysound.wav") attenuate(10) sound3 = @> audible(t -> 1000t .% 1,2s) # 2 second, 1 kHz saw tooth play(sound1,time=sound1_time) play(sound2,time=sound2_time) play(sound3,time=sound3_time) ``` TimedSound will carefully track the actual time the sound was played and issue a warning if need be. # Streams In addition to the discrete sounds that have been discussed so far, TimedSound also supports sound streams. Streams are arbitrarily long: you need not decide when they should stop until after they start playing. All of the primitives described so far can apply to streams (including concatenation), except that streams cannot be indexed. !!! note "Streaming operations are lazy" All manipulations of streams are lazy: they are applied just as the stream is played. The more operators you apply to a stream the more processing that has to occur during playback. If you have a particularly complicated stream you may have to increase streaming latency by changing the `stream_unit` parameter of [`setup_sound`](@ref), or consider an alternative approach (e.g. [`audible`](@ref)). To create a stream you can use one of the standard primitives, leaving out the length parameter. For example, the following will play a 1 kHz pure tone until julia quits. ```julia play(tone(1kHz)) ``` Streams always play on a specific stream channel, so if you want to stop the stream at some point you can request that the channel stop. The following plays a pure tone until something_happened() returns true. ```julia play(tone(1kHz),channel=1) while !something_happened() end stop(1) ``` Streams can be manipulated as they are playing as well, so if you wanted to have a ramp at the start and end of the stream to avoid clicks, you could change the example above, to the following. ```julia ongoing_tone = @> tone(1kHz) rampon play(ongoing_tone,channel=1) while !something_happened() end play(rampoff(ongoing_tone),channel=1) ``` !!! warning "Streams are stateful" This example also demonstrates the stateful nature of streams. Once some part of a stream has been played it is forever consumed, and cannot be played again. After the stream is played, subsequent modifications only apply to unplayed frames of the stream. *BEWARE*: this means that you cannot play two different modifications of the same stream. Just as with sound, manipulations to streams can be precisely timed. The following will turn the sound off precisely 1 second after something_happened() returns true. ```julia ongoing_tone = @> tone(1kHz) rampon play(ongoing_tone,channel=1) while !something_happened() end reference = at(1s) play(rampoff(ongoing_tone),channel=1,time=reference + 1s)) ``` If you wish to turn the entirety of a finite stream into a sound, you can use [`sound`](@ref). You can also grab the next section of an infinite stream using [`sound`](@ref) if you provide a second parameter specifying the length of the stream you want to turn into a sound. Some manipulations of streams require that the stream be treated as a sound. You can modify individual sound segments as they play from the stream using [`audiofn`](@ref). (Calling [`audiofn`](@ref) on a sound, rather than a stream, is the same as applying the given function to the sound directly). ## Low-level Sound/Stream Generation Finally, if none of the functions above suit your purposes for generating sounds or streams, there are two more low-level approachs. You can use the function [`audible`](@ref) to define a sound or stream using a function `f(t)` or `f(i)` defining the amplitudes for any given time or index. Alternatively you can convert any array to a sound using [`sound`](@ref).

42.260638

471

0.74248

eng_Latn

0.998934

e96b11b21112ef5f8e09b6e1eaad2660b0456490

607

md

Markdown

contrib/debian/README.md

csignal-project/CsignalCore

4f64e9697dfbc28aea058377dd18828deec1b195

[ "MIT" ]

1

2018-08-22T21:15:30.000Z

contrib/debian/README.md

csignal-project/CsignalCore

4f64e9697dfbc28aea058377dd18828deec1b195

[ "MIT" ]

null

contrib/debian/README.md

csignal-project/CsignalCore

4f64e9697dfbc28aea058377dd18828deec1b195

[ "MIT" ]

1

2018-08-27T12:13:15.000Z

Debian ==================== This directory contains files used to package csignald/csignal-qt for Debian-based Linux systems. If you compile csignald/csignal-qt yourself, there are some useful files here. ## csignal: URI support ## csignal-qt.desktop (Gnome / Open Desktop) To install: sudo desktop-file-install csignal-qt.desktop sudo update-desktop-database If you build yourself, you will either need to modify the paths in the .desktop file or copy or symlink your csignal-qt binary to `/usr/bin` and the `../../share/pixmaps/csignal128.png` to `/usr/share/pixmaps` csignal-qt.protocol (KDE)

27.590909

110

0.741351

eng_Latn

0.913133

e96caee85fbf69751052b09d20a2b6773a8c9207

8,344

md

Markdown

docs/containers/includes/vs-2019/container-tools.md

MicrosoftDocs/visualstudio-docs.cs-cz

3861d52726f1a515cfa62d590513a3c7a1b8019b

[ "CC-BY-4.0", "MIT" ]

1

2020-05-20T07:48:22.000Z

docs/containers/includes/vs-2019/container-tools.md

MicrosoftDocs/visualstudio-docs.cs-cz

3861d52726f1a515cfa62d590513a3c7a1b8019b

[ "CC-BY-4.0", "MIT" ]

7

2018-10-02T15:01:11.000Z

2021-11-05T20:25:20.000Z

docs/containers/includes/vs-2019/container-tools.md

MicrosoftDocs/visualstudio-docs.cs-cz

3861d52726f1a515cfa62d590513a3c7a1b8019b

[ "CC-BY-4.0", "MIT" ]

7

2018-10-01T22:49:53.000Z

2021-10-09T11:24:44.000Z

--- title: Visual Studio nástroje kontejneru pro docker s ASP.NET v Windows author: ghogen description: naučte se používat nástroje Visual Studio 2019 a Docker for Windows ms.author: ghogen ms.date: 03/08/2021 ms.technology: vs-container-tools ms.topic: include ms.openlocfilehash: ba4a1f333a6039f84665269f8779228431c79238 ms.sourcegitcommit: 4efdab6a579b31927c42531bb3f7fdd92890e4ac ms.translationtype: MT ms.contentlocale: cs-CZ ms.lasthandoff: 10/26/2021 ms.locfileid: "130354592" --- pomocí Visual Studio můžete snadno sestavovat, ladit a spouštět aplikace v kontejneru .net, ASP.NET a ASP.NET Core a publikovat je do Azure Container Registry, docker Hub, Azure App Service nebo vlastního registru kontejneru. v tomto článku publikujeme aplikaci ASP.NET Core pro Azure Container Registry. ## <a name="prerequisites"></a>Požadavky * [Docker Desktop](https://hub.docker.com/editions/community/docker-ce-desktop-windows) * [Visual Studio 2019](https://visualstudio.microsoft.com/downloads) s nainstalovanou úlohou vývoj pro **Web**, úlohy **nástrojů Azure** a/nebo **.net Core pro vývoj pro různé platformy** * [Vývojové nástroje .NET Core](https://dotnet.microsoft.com/download/dotnet-core/) pro vývoj pomocí .NET Core * Pokud chcete publikovat Azure Container Registry, předplatné Azure. [Zaregistrujte si bezplatnou zkušební verzi](https://azure.microsoft.com/free/dotnet/). ## <a name="installation-and-setup"></a>Instalace a nastavení pro instalaci docker si nejdřív přečtěte informace v části [docker Desktop, kde Windows: co potřebujete znát před instalací](https://docs.docker.com/docker-for-windows/install/#what-to-know-before-you-install)nástroje. Dále nainstalujte [Docker Desktop](https://hub.docker.com/editions/community/docker-ce-desktop-windows). ## <a name="add-a-project-to-a-docker-container"></a>Přidání projektu do kontejneru Docker 1. vytvořte nový projekt pomocí šablony **ASP.NET Core webové aplikace** , nebo pokud chcete použít .NET Framework místo .net Core, vyberte **ASP.NET webová aplikace (.NET Framework)**. 1. Na obrazovce **vytvořit novou webovou aplikaci** se ujistěte, že je zaškrtnuté políčko **Povolit podporu Docker** . ![Snímek obrazovky se zaškrtávacím políčkem Povolit podporu Docker.](../../media/container-tools/vs-2019/webapp-additional-information-31-docker.png) Snímek obrazovky ukazuje .NET Core; pokud používáte .NET Framework, vypadá to trochu odlišně. 1. vyberte typ požadovaného kontejneru (Windows nebo Linux) a klikněte na **vytvořit**. ## <a name="dockerfile-overview"></a>Souboru Dockerfile – přehled *Souboru Dockerfile* je v projektu vytvořen recept pro vytvoření finální image Docker. Porozumění příkazům, které jsou v něm, najdete v [referenčních informacích k souboru Dockerfile](https://docs.docker.com/engine/reference/builder/) : ```dockerfile FROM mcr.microsoft.com/dotnet/core/aspnet:3.1 AS base WORKDIR /app EXPOSE 80 EXPOSE 443 FROM mcr.microsoft.com/dotnet/core/sdk:3.1 AS build WORKDIR /src COPY ["WebApplication1/WebApplication1.csproj", "WebApplication1/"] RUN dotnet restore "WebApplication1/WebApplication1.csproj" COPY . . WORKDIR "/src/WebApplication1" RUN dotnet build "WebApplication1.csproj" -c Release -o /app/build FROM build AS publish RUN dotnet publish "WebApplication1.csproj" -c Release -o /app/publish FROM base AS final WORKDIR /app COPY --from=publish /app/publish . ENTRYPOINT ["dotnet", "WebApplication1.dll"] ``` Předchozí *souboru Dockerfile* vychází z image [Microsoft/aspnetcore](https://hub.docker.com/r/microsoft/aspnetcore/) a obsahuje pokyny pro úpravu základní image sestavením projektu a jeho přidáním do kontejneru. pokud používáte .NET Framework, bude základní image odlišná. Když je zaškrtnuté políčko **Konfigurovat pro protokol HTTPS** v dialogovém okně Nový projekt, *souboru Dockerfile* zpřístupňuje dva porty. Pro přenosy HTTP se používá jeden port; druhý port se používá pro protokol HTTPS. Pokud políčko není zaškrtnuté, bude pro přenosy HTTP vystaven jeden port (80). ## <a name="debug"></a>Ladění V rozevíracím seznamu ladění na panelu nástrojů vyberte **Docker** a spusťte ladění aplikace. Může se zobrazit zpráva s výzvou k důvěřování certifikátu. Chcete-li pokračovat, vyberte možnost důvěryhodného certifikátu. V okně **výstup** se zobrazí možnost **nástroje kontejneru** , kde se zobrazují akce, které probíhají. Poprvé může chvíli trvat, než se stáhne základní image, ale v dalších spuštěních je mnohem rychlejší. >[!NOTE] > Pokud potřebujete změnit porty pro ladění, můžete to udělat v souboru *launchSettings. JSON* . viz [Nastavení spuštění kontejneru](../../container-launch-settings.md). ## <a name="containers-window"></a>Okno kontejnery pokud máte Visual Studio 2019 verze 16,4 nebo novější, můžete použít okno **kontejnery** k zobrazení spuštěných kontejnerů na vašem počítači a také imagí, které máte k dispozici. Otevřete okno **kontejnery** pomocí vyhledávacího pole v integrovaném vývojovém prostředí (pokud ho chcete použít, stiskněte klávesu **CTRL** + **Q** ), zadejte `container` a zvolte okno **kontejnery** ze seznamu. Okno **kontejnery** můžete připojit na vhodné místo, například pod editorem, přesunutím kolem a podle vodítek umístění okna. V okně Najděte svůj kontejner a krok na každé kartě, abyste zobrazili proměnné prostředí, mapování portů, protokoly a systém souborů. ![Snímek okna kontejnerů](../../media/overview/vs-2019/container-tools-window.png) Další informace najdete v tématu [použití okna kontejnery](../../view-and-diagnose-containers.md). ## <a name="publish-docker-images"></a>Publikování imagí Docker Jakmile se cyklus vývoje a ladění aplikace dokončí, můžete vytvořit provozní image aplikace. 1. Změňte rozevírací seznam konfigurace na **vydaná** a sestavte aplikaci. 1. V **Průzkumník řešení** klikněte pravým tlačítkem na projekt a vyberte **publikovat**. 1. V dialogovém okně **publikovat** vyberte kartu **Docker Container Registry** . ![Snímek obrazovky dialogového okna pro publikování – vyberte Docker Container Registry.](../../media/container-tools/vs-2019/docker-container-registry.png) 1. Vyberte **vytvořit novou Azure Container Registry**. ![Snímek obrazovky dialogového okna pro publikování – vyberte vytvořit novou Azure Container Registry.](../../media/container-tools/vs-2019/select-existing-or-create-new-azure-container-registry.png) 1. Do pole **vytvořit nový Azure Container Registry** zadejte požadované hodnoty. | Nastavení | Navrhovaná hodnota | Popis | | ------------ | ------- | -------------------------------------------------- | | **Předpona DNS** | Globálně jedinečný název | Název, který jedinečně identifikuje váš registr kontejneru. | | **Předplatné** | Zvolte vaše předplatné. | Předplatné Azure, které se má použít. | | **[Skupina prostředků](/azure/azure-resource-manager/resource-group-overview)** | myResourceGroup | Název skupiny prostředků, ve které se má vytvořit registr kontejneru Pokud chcete vytvořit novou skupinu prostředků, zvolte **Nová**.| | **[SKU](/azure/container-registry/container-registry-skus)** | Standard | Úroveň služby registru kontejneru | | **Umístění registru** | Umístění, které je blízko vás | Vyberte umístění v [oblasti](https://azure.microsoft.com/regions/) poblíž nebo v blízkosti jiných služeb, které budou používat váš registr kontejneru. | ![snímek obrazovky dialogového okna pro vytvoření Azure Container Registry Visual Studio][0] 1. Klikněte na **Vytvořit**. Dialog **publikovat** teď zobrazuje vytvořený registr. ![Snímek obrazovky s dialogem pro publikování zobrazující Azure Container Registry vytvořena](../../media/container-tools/vs-2019/created-azure-container-registry.png) 1. Pokud chcete dokončit proces publikování image kontejneru do nově vytvořeného registru v Azure, klikněte na **Dokončit** . ![Snímek obrazovky zobrazující úspěšné publikování](../../media/container-tools/vs-2019/publish-succeeded.png) ## <a name="next-steps"></a>Další kroky Kontejner teď můžete načíst z registru do libovolného hostitele, který podporuje spouštění imagí Docker, například [Azure Container Instances](/azure/container-instances/container-instances-tutorial-deploy-app). [0]:../../media/hosting-web-apps-in-docker/vs-azure-container-registry-provisioning-dialog-2019.png

62.736842

323

0.767857

ces_Latn

0.998339

e96cb72c1c72b075c5ec19d1d89a2596d01e2428

1,555

md

Markdown

articles/python/quickstarts-cognitive-services.md

hyoshioka0128/azure-dev-docs.ja-jp

0d7d0b6f3c056c00d71ef246bbbd84f99f61407b

[ "CC-BY-4.0", "MIT" ]

null

articles/python/quickstarts-cognitive-services.md

hyoshioka0128/azure-dev-docs.ja-jp

0d7d0b6f3c056c00d71ef246bbbd84f99f61407b

[ "CC-BY-4.0", "MIT" ]

null

articles/python/quickstarts-cognitive-services.md

hyoshioka0128/azure-dev-docs.ja-jp

0d7d0b6f3c056c00d71ef246bbbd84f99f61407b

[ "CC-BY-4.0", "MIT" ]

null

--- title: Azure の Python アプリでの Cognitive Services のクイックスタート description: Python アプリの Cognitive Services に関する Azure ドキュメントの概要に関する資料の一覧です。 ms.date: 03/17/2020 ms.topic: conceptual ms.openlocfilehash: 8a42fb086cbad0691f874bdaf8b08486af9f70ea ms.sourcegitcommit: be67ceba91727da014879d16bbbbc19756ee22e2 ms.translationtype: HT ms.contentlocale: ja-JP ms.lasthandoff: 05/05/2020 ms.locfileid: "80442107" --- # <a name="cognitive-services-for-python-apps-on-azure"></a>Azure の Python アプリでの Cognitive Services 次の記事は、Azure Cognitive Services を開始する際に役立ちます。 - [Python 用 Azure Cognitive Services モジュール](/python/api/overview/azure/cognitive-services?view=azure-python) - [Computer Vision の REST API と Python を使用してリモート画像を分析する](/azure/cognitive-services/Computer-vision/Quickstarts/python-analyze) - [Custom Vision Python SDK を使用して画像分類プロジェクトを作成する](/azure/cognitive-services/custom-vision-service/python-tutorial) - [Python による顔認識](/azure/cognitive-services/face/quickstarts/python-sdk) - [Python 用の Language Understanding (LUIS) オーサリング](/azure/cognitive-services/luis/sdk-authoring) - [Python 用 Text Analytics クライアントライブラリを使用する](/azure/cognitive-services/text-analytics/quickstarts/text-analytics-sdk) - [Bing Autosuggest REST API と Python によって検索クエリの候補を表示する](/azure/cognitive-services/bing-autosuggest/quickstarts/python) - [Python 用 Content Moderator クライアントライブラリを使用する](/azure/cognitive-services/content-moderator/python-sdk-quickstart) - [音声サービスハブページ](/azure/cognitive-services/speech-service/index) - [検索ハブページ](/azure/cognitive-services/bing-web-search/index)

57.592593

126

0.81672

yue_Hant

0.524363

e96e0bbb590eeaea7e46f06a33b2e7b82b41ed1c

5,443

md

Markdown

README.md

textcreationpartnership/A76894

619314d3732c23e1eceb75dba251bfe4a3c00279

[ "CC0-1.0" ]

null

README.md

textcreationpartnership/A76894

619314d3732c23e1eceb75dba251bfe4a3c00279

[ "CC0-1.0" ]

null

README.md

textcreationpartnership/A76894

619314d3732c23e1eceb75dba251bfe4a3c00279

[ "CC0-1.0" ]

null

#Bloudy newes from Holland: being a true relation of the present proceedings of the Dutch-men against the English, at the Hague, Amsterdam, Rotterdam, Brill, Dort, Flushin, and divers other places. Also, a great fight at sea, between the Parliaments ships, and the Hollanders; the number burnt, sunk, and taken, by Captain Johnson and the rest of the English; with the manner of the said engagement. Likewise Lieu. Colonel John Lilburn made Captain of a man of War for the States of Holland, and his letter to the Lord General Cromwel.# Bloudy newes from Holland: being a true relation of the present proceedings of the Dutch-men against the English, at the Hague, Amsterdam, Rotterdam, Brill, Dort, Flushin, and divers other places. Also, a great fight at sea, between the Parliaments ships, and the Hollanders; the number burnt, sunk, and taken, by Captain Johnson and the rest of the English; with the manner of the said engagement. Likewise Lieu. Colonel John Lilburn made Captain of a man of War for the States of Holland, and his letter to the Lord General Cromwel. ##General Summary## **Links** [TCP catalogue](http://www.ota.ox.ac.uk/tcp/) • [HTML](http://tei.it.ox.ac.uk/tcp/Texts-HTML/free/A76/A76894.html) • [EPUB](http://tei.it.ox.ac.uk/tcp/Texts-EPUB/free/A76/A76894.epub) • [Page images (Historical Texts)](https://historicaltexts.jisc.ac.uk/eebo-99865744e) **Availability** To the extent possible under law, the Text Creation Partnership has waived all copyright and related or neighboring rights to this keyboarded and encoded edition of the work described above, according to the terms of the CC0 1.0 Public Domain Dedication (http://creativecommons.org/publicdomain/zero/1.0/). This waiver does not extend to any page images or other supplementary files associated with this work, which may be protected by copyright or other license restrictions. Please go to https://www.textcreationpartnership.org/ for more information about the project. **Major revisions** 1. __2012-06__ __TCP__ *Assigned for keying and markup* 1. __2012-07__ __SPi Global__ *Keyed and coded from ProQuest page images* 1. __2012-08__ __Geremy Carnes__ *Sampled and proofread* 1. __2012-08__ __Geremy Carnes__ *Text and markup reviewed and edited* 1. __2013-02__ __pfs__ *Batch review (QC) and XML conversion* ##Content Summary## #####Front##### BLOUDY NEWES FROM HOLLAND: BEING A true Relation of the preſent Proceedings of the Dutch-men againſt #####Body##### 1. A Bloudy Fight at Sea, between the Parliaments ſhips, under the Command of Captain Vice-Admiral Clerk, Captain Penington, and Captain Armſtrong; and the Hollanders, commanded by Vice-Admiral Frederick. With the particulars of the Fight, the manner of their Engagement; and the number of ſhips, men, and Ordnance, ſunk, killed and taken. _ Sent in a Letter from Captain Owen, aboard the Dragon in the Downs, March 15, 1652. SIR,THere hath been a great and imperial Councel held at Munſter in Germany, by the Ambaſſadors of 1 **Types of content** * Oh, Mr. Jourdain, there is **prose** in there! There are 1 **omitted** fragments! @__reason__ (1) : illegible (1) • @__resp__ (1) : #MURP (1) • @__extent__ (1) : 1 letter (1) **Character listing** |Text|string(s)|codepoint(s)| |---|---|---| |Latin Extended-A|ſ|383| |General Punctuation|•|8226| ##Tag Usage Summary## ###Header Tag Usage### |No|element name|occ|attributes| |---|---|---|---| |1.|__availability__|1|| |2.|__biblFull__|1|| |3.|__change__|5|| |4.|__date__|8| @__when__ (1) : 2013-12 (1)| |5.|__edition__|1|| |6.|__editionStmt__|1|| |7.|__editorialDecl__|1|| |8.|__encodingDesc__|1|| |9.|__extent__|2|| |10.|__fileDesc__|1|| |11.|__idno__|7| @__type__ (7) : DLPS (1), STC (3), EEBO-CITATION (1), PROQUEST (1), VID (1)| |12.|__keywords__|1| @__scheme__ (1) : http://authorities.loc.gov/ (1)| |13.|__label__|5|| |14.|__langUsage__|1|| |15.|__language__|1| @__ident__ (1) : eng (1)| |16.|__listPrefixDef__|1|| |17.|__note__|5|| |18.|__notesStmt__|2|| |19.|__p__|11|| |20.|__prefixDef__|2| @__ident__ (2) : tcp (1), char (1) • @__matchPattern__ (2) : ([0-9\-]+):([0-9IVX]+) (1), (.+) (1) • @__replacementPattern__ (2) : http://eebo.chadwyck.com/downloadtiff?vid=$1&page=$2 (1), https://raw.githubusercontent.com/textcreationpartnership/Texts/master/tcpchars.xml#$1 (1)| |21.|__profileDesc__|1|| |22.|__projectDesc__|1|| |23.|__pubPlace__|2|| |24.|__publicationStmt__|2|| |25.|__publisher__|2|| |26.|__ref__|1| @__target__ (1) : http://www.textcreationpartnership.org/docs/. (1)| |27.|__revisionDesc__|1|| |28.|__seriesStmt__|1|| |29.|__sourceDesc__|1|| |30.|__term__|6|| |31.|__textClass__|1|| |32.|__title__|3|| |33.|__titleStmt__|2|| ###Text Tag Usage### |No|element name|occ|attributes| |---|---|---|---| |1.|__body__|1|| |2.|__closer__|1|| |3.|__date__|1|| |4.|__dateline__|1|| |5.|__desc__|1|| |6.|__div__|4| @__type__ (4) : title_page (1), account (1), letter (2)| |7.|__front__|1|| |8.|__g__|33| @__ref__ (33) : char:EOLhyphen (33)| |9.|__gap__|1| @__reason__ (1) : illegible (1) • @__resp__ (1) : #MURP (1) • @__extent__ (1) : 1 letter (1)| |10.|__head__|2|| |11.|__hi__|11|| |12.|__opener__|2|| |13.|__p__|12|| |14.|__pb__|8| @__facs__ (8) : tcp:117995:1 (1), tcp:117995:2 (2), tcp:117995:3 (2), tcp:117995:4 (2), tcp:117995:5 (1) • @__rendition__ (1) : simple:additions (1) • @__n__ (6) : 3 (1), 4 (1), 5 (1), 6 (1), 7 (1), 8 (1)| |15.|__salute__|2|| |16.|__trailer__|1||

49.036036

570

0.708249

eng_Latn

0.805307

e96e5cea14716427e01f51149956203d99fa7d22

719

md

Markdown

content_zh/docs/setup/kubernetes/platform-setup/minikube/index.md

WallaceTan/istio.github.io

75dbb17ff1e49751dfd2856659b3f200343ebc3f

[ "Apache-2.0" ]

null

content_zh/docs/setup/kubernetes/platform-setup/minikube/index.md

WallaceTan/istio.github.io

75dbb17ff1e49751dfd2856659b3f200343ebc3f

[ "Apache-2.0" ]

null

content_zh/docs/setup/kubernetes/platform-setup/minikube/index.md

WallaceTan/istio.github.io

75dbb17ff1e49751dfd2856659b3f200343ebc3f

[ "Apache-2.0" ]

null

--- title: Minikube description: 对 Minikube 集群进行配置以便安装运行 Istio weight: 15 keywords: [platform-setup,kubernetes,minikube] --- 依照本指南对 Minikube 集群进行配置以便安装运行 Istio。 1. 要在本地运行 Istio，可以安装最新版本的 [Minikube](https://kubernetes.io/docs/setup/minikube/)（**0.28.0 或更高**） 1. 选择一个[虚拟机驱动](https://kubernetes.io/docs/setup/minikube/#quickstart)，安装之后，这里假设所选驱动为 `your_vm_driver_choice`，完成下面的步骤：如果是 Kubernetes **1.9**： {{< text bash >}} $ minikube start --memory=4096 --kubernetes-version=v1.9.4 --vm-driver=`your_vm_driver_choice` {{< /text >}} 如果是 Kubernetes **1.10**： {{< text bash >}} $ minikube start --memory=4096 --kubernetes-version=v1.10.0 --vm-driver=`your_vm_driver_choice` {{< /text >}}

28.76

117

0.688456

yue_Hant

0.165074

e96e60a8c1ca0c28dcade65322acbaf07c69316f

2,910

md

Markdown

Programming with C#/1. C# Fundamentals I/02. Primitive Data Types and Variables/Readme.md

elena-andonova/telerik-academy

1dc9daf75c06694b887253d52492d0df1a5bdbe3

[ "MIT" ]

2

2019-04-14T21:04:43.000Z

2019-07-10T05:04:44.000Z

Programming with C#/1. C# Fundamentals I/02. Primitive Data Types and Variables/Readme.md

elena-andonova/telerik-academy

1dc9daf75c06694b887253d52492d0df1a5bdbe3

[ "MIT" ]

null

Programming with C#/1. C# Fundamentals I/02. Primitive Data Types and Variables/Readme.md

elena-andonova/telerik-academy

1dc9daf75c06694b887253d52492d0df1a5bdbe3

[ "MIT" ]

3

2015-05-11T06:50:35.000Z

2016-12-05T12:07:09.000Z

## Primitive Data Types and Variables 1. Declare five variables choosing for each of them the most appropriate of the types `byte`, `sbyte`, `short`, `ushort`, `int`, `uint`, `long`, `ulong` to represent the following values: 52130, -115, 4825932, 97, -10000. * Which of the following values can be assigned to a variable of type `float` and which to a variable of type `double`: 34.567839023, 12.345, 8923.1234857, 3456.091? * Write a program that safely compares floating-point numbers with precision of **0.000001**. Example: (5.3 ; 6.01) -> false; (5.00000001 ; 5.00000003) -> true * Declare an integer variable and assign it with the value **254** in hexadecimal format. Use Windows Calculator to find its hexadecimal representation. * Declare a character variable and assign it with the symbol that has Unicode code **72**. Hint: first use the Windows Calculator to find the hexadecimal representation of 72. * Declare a boolean variable called `isFemale` and assign an appropriate value corresponding to your gender. * Declare two string variables and assign them with **"Hello"** and **"World"**. Declare an `object` variable and assign it with the concatenation of the first two variables (mind adding an interval). Declare a third `string` variable and initialize it with the value of the object variable (you should perform type casting). * Declare two string variables and assign them with following value: > The "use" of quotations causes difficulties. Do the above in two different ways: with and without using quoted strings. * Write a program that prints an isosceles triangle of 9 copyright symbols `©`. Use Windows Character Map to find the Unicode code of the `©` symbol. Note: the `©` symbol may be displayed incorrectly. * A marketing firm wants to keep record of its employees. Each record would have the following characteristics – first name, family name, age, gender (m or f), ID number, unique employee number (27560000 to 27569999). Declare the variables needed to keep the information for a single employee using appropriate data types and descriptive names. * Declare two integer variables and assign them with **5** and **10** and after that exchange their values. * Find online more information about **ASCII** (American Standard Code for Information Interchange) and write a program that prints the entire ASCII table of characters on the console. * Create a program that assigns `null` values to an integer and to double variables. Try to print them on the console, try to add some values or the null literal to them and see the result. * A bank account has a holder name (first name, middle name and last name), available amount of money (balance), bank name, IBAN, BIC code and 3 credit card numbers associated with the account. Declare the variables needed to keep the information for a single bank account using the appropriate data types and descriptive names.

138.571429

344

0.771134

eng_Latn

0.999043

e96efa57c2310c9b7ec8496828cefc40ab581f06

1,291

md

Markdown

docs/en/ref-guide-template/supplemental.md

odoe/framework

f8a27a4cd8bceddda8c9e7c7b50bf08f70750950

[ "BSD-3-Clause" ]

543

2018-07-10T00:10:10.000Z

2022-03-31T02:18:14.000Z

docs/en/ref-guide-template/supplemental.md

odoe/framework

f8a27a4cd8bceddda8c9e7c7b50bf08f70750950

[ "BSD-3-Clause" ]

626

2018-07-12T15:23:10.000Z

2022-01-27T16:55:23.000Z

docs/en/ref-guide-template/supplemental.md

odoe/framework

f8a27a4cd8bceddda8c9e7c7b50bf08f70750950

[ "BSD-3-Clause" ]

83

2018-07-09T20:19:07.000Z

2022-03-30T06:48:29.000Z

# Feature X in detail The supplemental.md file should fully describe all features that the capability offers. ## Feature X.x Further subsections describing particular topics for a given feature. Possibly also [linking to other related sections within the reference guide](./basic-usage.md#feature-x). ```tsx // including fully-working embedded code snippets as further illustration import WidgetBase from '@dojo/framework/core/WidgetBase'; import { tsx } from '@dojo/framework/core/vdom'; export default class MyWidget extends WidgetBase { protected render() { return <div>My Widget</div>; } } ``` ### `CapabilityX` Methods - `featureXmethod(foo: boolean)` - Can also include inline API documentation to round out the description of a feature. ### `DataStructureX` Properties - `sampleProperty?: string | string[]` - API documentation is also likely to include descriptions of relevant data models that users need to interact with when working with a feature. ## Feature X.y ... # Feature Y in detail ... # (Optional) Further examples of the capability ## Feature X [Links out to further examples that illustrate a capability or feature](https://codesandbox.io/s/github/dojo/dojo-codesandbox-template/tree/master/) in a more complete, real-world context.

29.340909

188

0.75213

eng_Latn

0.995351

e970ad817494e016f8c177587236cb3c56cd69e1

1,777

md

Markdown

src/pages/index.md

jakobgn/gatsby-starter-netlify-cms

2a2be22ed26f120ab6a39dff7aaf3b21b75285df

[ "MIT" ]

null

src/pages/index.md

jakobgn/gatsby-starter-netlify-cms

2a2be22ed26f120ab6a39dff7aaf3b21b75285df

[ "MIT" ]

null

src/pages/index.md

jakobgn/gatsby-starter-netlify-cms

2a2be22ed26f120ab6a39dff7aaf3b21b75285df

[ "MIT" ]

null

--- templateKey: index-page title: Vi vil hjælpe den enkelte med at opnå finansiel indsigt og uafhængighed heading: Produkter mainpitch: description: | Det tror vi på. I dag er det rigtig dyrt at få god finansiel rådgivning. title: Kan finansiel rådgivning gøres bedre? intro: blurbs: - image: /img/undraw_folder_39kl.png heading: Neway.dk text: > Neway er en gratis service til den enkelte private bruger. Det er en let og overskuelig måde for slutbrugeren at bevare sine finansielle data trygt og GDPR rigtigt, med mulighed for sikker deling til rådgivere. Slutbrugeren kan igennem Neway følge med i udviklingen af de større økonomiske poster såsom pensioner og investeringer. - image: /img/undraw_envelope_n8lc.png heading: Pensionsinfo Scraper text: > Denne service kræver, at brugeren vil uploade en pensionsinfo PDF fil. Servicen indlæser oplysningerne fra PDFen og generere et maskinlæsbart format (Json eller XML). - image: /img/undraw_notify_88a4.png heading: PensionsTjek text: > Næsten 70% af alle danskere har glemte eller inaktive pensionsordninger fra tidligere arbejdspladser. Derved smider de mange penge ud af vinduet ved at betale for meget i omkostninger eller ved at være placeret i de forkerte puljer. Denne service giver en løbende status over udviklingen af brugerens pensionsordninger og hjælper med at identificere eventuelle problemer. - image: /img/undraw_teacher_35j2.png heading: PensionsTjek Business text: > I samarbejde med pensionsmæglere og rådgivere tilbyder Neway en udvidet løbende pensionstjek som en virksomhedsordning. ---

42.309524

94

0.718064

dan_Latn

0.999667

e9721c246338e3b10c35a4d311bc8a1399ecf8da

25,428

md

Markdown

content/sketches/steviephysics/index.md

StevenSchuerstedt/web-page

d34479bd2b0d8b449e4679a5ab806f011a116f8f

[ "MIT" ]

null

content/sketches/steviephysics/index.md

StevenSchuerstedt/web-page

d34479bd2b0d8b449e4679a5ab806f011a116f8f

[ "MIT" ]

6

2021-08-17T13:09:47.000Z

2021-12-19T15:54:42.000Z

content/sketches/steviephysics/index.md

StevenSchuerstedt/web-page

d34479bd2b0d8b449e4679a5ab806f011a116f8f

[ "MIT" ]

null

--- title: SteviePhysics author: admin type: page date: 2021-04-14T14:34:04.000Z draft: false private: true published: true --- Simple Physik Engine für 2D. Nicht für Spiele bzw. interaktive Echtzeitanwendungen sondern einfach nur viel Physik. Gute Möglichkeit um die physikalischen Formel in der “Praxis” auszuprobieren. ### Der Schiefe Wurf, ein einfacher Start Wir befinden uns in der klassischen Mechanik und beginnen mit Newtons Gesetzt. “Kraft gleich Masse mal Beschleunigung”. Was ist Kraft? Da hört unsere Vorstellung auf, aber es funktioniert ja alles gut. <img loading="lazy" src="https://steven.schuerstedt.com/wp-content/ql-cache/quicklatex.com-0f6fd211837af29e0081f0a8ff39ebb7_l3.png" class="ql-img-inline-formula quicklatex-auto-format" alt="\vec{F} = m\vec{a}" title="Rendered by QuickLaTeX.com" height="17" width="64" style="vertical-align: 0px;" /> Zu beachten ist das sowohl die Kraft als auch die Beschleunigung eine vektorielle Größe sind, also eine Richtung haben. Beschleunigung ist nichts anderes als die Änderung der Geschwindigkeit, und Geschwindigkeit ist die Änderung der Position. Für die Position interessieren uns wir dann letztendlich auch, der Rest existiert ja nur “gedacht”. <img loading="lazy" src="https://steven.schuerstedt.com/wp-content/ql-cache/quicklatex.com-df12924a040b980ba09bff4ccd969178_l3.png" class="ql-img-inline-formula quicklatex-auto-format" alt="\vec{a}(t) = \ddot{x}(t) = \frac{d^2x(t)}{dt^2}" title="Rendered by QuickLaTeX.com" height="27" width="147" style="vertical-align: -7px;" /> Jetzt legen wir los mit dem Schiefen Wurf, die einzige Kraft die hier Wirkt ist die Gravitation, in der einfachsten Darstellung: <img loading="lazy" src="https://steven.schuerstedt.com/wp-content/ql-cache/quicklatex.com-9fc32e1ac6a736303793a721f4857151_l3.png" class="ql-img-inline-formula quicklatex-auto-format" alt="\vec{F} = -m\vec{g}, \vec{g} = \left(\begin{array}{c} 0 \\ 9.81 \end{array}\right)" title="Rendered by QuickLaTeX.com" height="43" width="187" style="vertical-align: -17px;" /> Das minus und das<img loading="lazy" src="https://steven.schuerstedt.com/wp-content/ql-cache/quicklatex.com-d3d6d1d954ef1c89c93a91c57d9006ec_l3.png" class="ql-img-inline-formula quicklatex-auto-format" alt="\vec{g}" title="Rendered by QuickLaTeX.com" height="17" width="11" style="vertical-align: -4px;" /> in der y-Komponente wirkt ist hier erstmal willkürlich gewählt und hängt natürlich vom Koordinatensystem ab. Eingesetzt bekommen wir die erste Differenzialgleichung, die jetzt noch recht simpel ist. <img loading="lazy" src="https://steven.schuerstedt.com/wp-content/ql-cache/quicklatex.com-f68e1d00ee7973b315f6c5c6c507be96_l3.png" class="ql-img-inline-formula quicklatex-auto-format" alt="-m\vec{g} = m\ddot{x}(t)" title="Rendered by QuickLaTeX.com" height="19" width="106" style="vertical-align: -5px;" /> Diese Gleichung beschreibt die Bewegung von unseren Körper und wir können sie benutzen um<img loading="lazy" src="https://steven.schuerstedt.com/wp-content/ql-cache/quicklatex.com-5fdd870f5a4b1b070c7d28c0b60eeb31_l3.png" class="ql-img-inline-formula quicklatex-auto-format" alt="x(t)" title="Rendered by QuickLaTeX.com" height="19" width="29" style="vertical-align: -5px;" /> auszurechnen, also die Position des Körpers abhängig von der Zeit, denn die Position ist alles was uns letztendlich interessiert. Generell gibt es bei Differenzialgleichungen mehrere Lösungsstrategien, bei dieser einfachen können wir direkt zwei mal Integrieren und erhalten: <img loading="lazy" src="https://steven.schuerstedt.com/wp-content/ql-cache/quicklatex.com-e93b91b5fcff45198cc4ee84ad1351d1_l3.png" class="ql-img-inline-formula quicklatex-auto-format" alt="\vec{x(t)} = -\frac{1}{2}\vec{g}t^2+\vec{v_0}t+\vec{x_0}" title="Rendered by QuickLaTeX.com" height="25" width="185" style="vertical-align: -6px;" /> Unsere Differenzialgleichung hat nicht eine eindeutige Lösung, sondern unendlich viele. Jede Funktion die zweimal abgeleitet gleich<img loading="lazy" src="https://steven.schuerstedt.com/wp-content/ql-cache/quicklatex.com-6fb9ee7a136e17046e37c3f6d20ee140_l3.png" class="ql-img-inline-formula quicklatex-auto-format" alt="-mg" title="Rendered by QuickLaTeX.com" height="12" width="38" style="vertical-align: -4px;" /> ergibt ist eine Lösung für unser Problem. Was übrig bleibt sind die Integrationskonstanten, bzw. die Anfangswerte.<img loading="lazy" src="https://steven.schuerstedt.com/wp-content/ql-cache/quicklatex.com-898badcd46de9bc8f635b2d11eeb344a_l3.png" class="ql-img-inline-formula quicklatex-auto-format" alt="\vec{v_0}" title="Rendered by QuickLaTeX.com" height="16" width="16" style="vertical-align: -3px;" /> beschreibt die Geschwindigkeit die der Körper am Anfang hatte und<img loading="lazy" src="https://steven.schuerstedt.com/wp-content/ql-cache/quicklatex.com-9f55f2a94c0f6960bc2c46c9b5a7da40_l3.png" class="ql-img-inline-formula quicklatex-auto-format" alt="\vec{x_0}" title="Rendered by QuickLaTeX.com" height="16" width="17" style="vertical-align: -3px;" /> den Anfangsort. Die Gleichung kann man jetzt genauso in einer Physik-Engine verwenden, um die Position von Objekten zu berechnen. #### Welche Annahmen wurden getroffen? Damit die Berechnung und das Modell funktioniert, wurden einige vereinfachende, idealisierende Annahmen getroffen. So haben wir beispielsweise die Luftreibung ignoriert, die Gravitation vereinfacht und auch die geometrische Beschaffenheit unseres Wurfobjektes ignoriert. Wenn wir unsere Simulation des schiefen Wurfes jetzt realistischer Gestalten möchten, wird es um einiges komplizierter und wir benötigen mehr Informationen über die eigentliche Sache die wir berechnen möchten. Werfen wir unser Objekt in Luft? Oder in einem anderen Medium Wasser? Befinden wir uns auf der Erde? Oder auf einen anderem Planeten, mit anderer Gravitation, welche Planeten befinden sich um uns herum, in welcher Entfernung? Hier stellt sich natürlich auch die Frage welche Fragen für das was wir mit der Physik Engine eigentlich machen wollen relevant sind. Im folgenden möchte ich anschneiden wie eine realistischere Beschreibung des schiefen Wurfes aussehen könnte. #### Schiefer Wurf mit Luftwiderstand Die Gleichung für die Luftwiderstandskraft lautet: <img loading="lazy" src="https://steven.schuerstedt.com/wp-content/ql-cache/quicklatex.com-47e81b0f57d688adff5ab85432fe9f3c_l3.png" class="ql-img-inline-formula quicklatex-auto-format" alt="F_{Luft} = \frac{1}{2} c  A \rho v^2" title="Rendered by QuickLaTeX.com" height="22" width="123" style="vertical-align: -6px;" /> interessant ist hierbei das die Gleichung proportional zum Quadrat der Geschwindigkeit ist, ein Umstand der z.b. beim Rennradfahren wichtig ist. Bei hohen Geschwindigkeiten in der Ebene spielt das Windschatten fahren eine große Rolle, bei Bergen hingegen ist es nicht wichtig. Die anderen Variablen beschreiben verschiedene Parameter die noch in die Gleichung mit einfließen,<img loading="lazy" src="https://steven.schuerstedt.com/wp-content/ql-cache/quicklatex.com-da039068127cf2ec5fc05123d4d3546f_l3.png" class="ql-img-inline-formula quicklatex-auto-format" alt="\rho" title="Rendered by QuickLaTeX.com" height="12" width="9" style="vertical-align: -4px;" /> ist die Dichte des Mediums,<img loading="lazy" src="https://steven.schuerstedt.com/wp-content/ql-cache/quicklatex.com-25b206f25506e6d6f46be832f7119ffa_l3.png" class="ql-img-inline-formula quicklatex-auto-format" alt="A" title="Rendered by QuickLaTeX.com" height="12" width="13" style="vertical-align: 0px;" /> die Fläche des Gegenstandes der auf die Luft trifft und<img loading="lazy" src="https://steven.schuerstedt.com/wp-content/ql-cache/quicklatex.com-41a04eeea923a1a0c28094a8a4680525_l3.png" class="ql-img-inline-formula quicklatex-auto-format" alt="c" title="Rendered by QuickLaTeX.com" height="8" width="8" style="vertical-align: 0px;" /> ein zusätzlicher Parameter für die Oberflächenbeschaffenheit und die Form. Woher diese Gleichung kommt und wieso genau diese Parameter eine Rolle spielen, ist eine gute Frage. Einige Parameter könnten auch zusätzlich von der Geschwindigkeit oder dem Ort abhängen, aber um zu überhaupt einen Ergebnis zu kommen müssen wir ständig Kompromisse eingehen und nicht zu viel Nachfragen. Die Kraft für den Luftwiderstand können wir nun mit der Gravitationskraft zusammenführen, um eine neue etwas genauere Differenzialgleichung für den Schiefen Wurf zu erhalten: <img loading="lazy" src="https://steven.schuerstedt.com/wp-content/ql-cache/quicklatex.com-656b3ea48c72116ed35793125fb7c8f4_l3.png" class="ql-img-inline-formula quicklatex-auto-format" alt="\vec{F} = -m\vec{g} - k \dot{x}^2" title="Rendered by QuickLaTeX.com" height="21" width="124" style="vertical-align: -4px;" /> . Das Vorzeichen bei der Luftwiderstandskraft stimmt jetzt nicht ganz, da der Luftwiderstand immer entgegen der Bewegung ist, die Gravitationskraft aber immer nach unten zeigt. Deswegen müssen wir den Wurf in drei Phasen unterteilen und die jeweiligen DGL lösen. Das setzt natürlich voraus das die Abhängigkeit von der Geschwindigkeit Komponenten weise Unabhängig ist, was eine weitere Vereinfachung darstellt. **Horizontal:** <img loading="lazy" src="https://steven.schuerstedt.com/wp-content/ql-cache/quicklatex.com-f8d13cee8546fdacacc955bc7e4ddacf_l3.png" class="ql-img-inline-formula quicklatex-auto-format" alt="m\ddot{x} = -k\dot{x}^2" title="Rendered by QuickLaTeX.com" height="15" width="90" style="vertical-align: 0px;" /> Diese DGL ist jetzt schon etwas komplizierter, um sie zu lösen gibt es mehrere Möglichkeiten, wir benützen Trennung der Veränderlichen und kommen auf: <img loading="lazy" src="https://steven.schuerstedt.com/wp-content/ql-cache/quicklatex.com-ff5edb62b89211afacb33b734be191db_l3.png" class="ql-img-inline-formula quicklatex-auto-format" alt="x(t)_{hor} = \frac{m}{k} ln(\frac{k}{m} \dot{x}_0 t +1)" title="Rendered by QuickLaTeX.com" height="22" width="192" style="vertical-align: -6px;" /> Siehe: https://matheplanet.com/default3.html?call=article.php?sid=735 **Vertikal:** In vertikaler Richtung kann die Luftwiderstandskraft jetzt einmal entgegen der Gravitation wirken und in Richtung der Gravitation, also: (I)<img loading="lazy" src="https://steven.schuerstedt.com/wp-content/ql-cache/quicklatex.com-7cbbeb2a4f9ffc614c72d46ef0d2e9ad_l3.png" class="ql-img-inline-formula quicklatex-auto-format" alt="m\ddot{x} = -k\dot{x}^2 - mg" title="Rendered by QuickLaTeX.com" height="19" width="137" style="vertical-align: -4px;" /> (II)<img loading="lazy" src="https://steven.schuerstedt.com/wp-content/ql-cache/quicklatex.com-8befd872396f8a4165d31e67106e7757_l3.png" class="ql-img-inline-formula quicklatex-auto-format" alt="m\ddot{x} = k\dot{x}^2 -mg" title="Rendered by QuickLaTeX.com" height="19" width="124" style="vertical-align: -4px;" /> Hier wird es nun schon ziemlich kompliziert und unhandlich, da beide DGLs keine einfache Lösung besitzen. Für die erste Gleichung kann man wieder Trennung der Veränderlichen benützen und muss dann nicht ganz einfache Integrale lösen. Das Ergebnis ist dann: (I)<img loading="lazy" src="https://steven.schuerstedt.com/wp-content/ql-cache/quicklatex.com-93a8eb4a69a4bff2aba596115fc7ca60_l3.png" class="ql-img-inline-formula quicklatex-auto-format" alt="y(t)_{aufwärts} = \frac{v_{s}^2}{g}*(ln(cos(\frac{g(t_U - t)}{v_s})) - ln(cos(\frac{gt_U}{v_s})))" title="Rendered by QuickLaTeX.com" height="29" width="397" style="vertical-align: -9px;" /> mit<img loading="lazy" src="https://steven.schuerstedt.com/wp-content/ql-cache/quicklatex.com-86172a705910222f57932a2aa476cdbe_l3.png" class="ql-img-inline-formula quicklatex-auto-format" alt="v_s = \sqrt{\frac{mg}{k}}" title="Rendered by QuickLaTeX.com" height="32" width="81" style="vertical-align: -11px;" /> und<img loading="lazy" src="https://steven.schuerstedt.com/wp-content/ql-cache/quicklatex.com-1196ef0c219323c6a7b6802bc1d8444a_l3.png" class="ql-img-inline-formula quicklatex-auto-format" alt="t_U = \frac{v_s}{g}atan(\frac{\dot{y}_0}{v_s})" title="Rendered by QuickLaTeX.com" height="26" width="125" style="vertical-align: -9px;" /> und (II)<img loading="lazy" src="https://steven.schuerstedt.com/wp-content/ql-cache/quicklatex.com-a51aa0ce1270fbd777a56e3e271e12dd_l3.png" class="ql-img-inline-formula quicklatex-auto-format" alt="y(t)_{abwärts} = -\frac{v_sg(t-t_U)}{g}-\frac{v_s^2}{g}ln(\frac{1+e^{-\frac{2g(t-t_U)}{v_s}}}{2} cos(\frac{gt_U}{v_s}))" title="Rendered by QuickLaTeX.com" height="38" width="407" style="vertical-align: -9px;" /> Wenn wir jetzt etwas genauer werde wollen und nicht mehr annehmen das die Reibekraft unabhängig in x- und y-Richtung wirkt, sondern vom Betragsquadrat der Geschwindigkeit abhängt, dann haben wir ein Problem. Die dann erhaltene DGL ist nicht mehr analytisch lösbar. #### Numerisches Lösen der Bewegungsgleichungen Um die Newton Bewegungsleichungen numerisch zu lösen, formulieren wir die DGL zweiter Ordnung in zwei Gleichungen erster Ordnung um. <img loading="lazy" src="https://steven.schuerstedt.com/wp-content/ql-cache/quicklatex.com-ada573b9d4aab29758cbd3ab4fa2351c_l3.png" class="ql-img-inline-formula quicklatex-auto-format" alt="F = m\ddot{x}" title="Rendered by QuickLaTeX.com" height="12" width="63" style="vertical-align: 0px;" /> => eine Gleichung zweiter Ordnung <img loading="lazy" src="https://steven.schuerstedt.com/wp-content/ql-cache/quicklatex.com-cbf5de5e08b3a0869683046035183987_l3.png" class="ql-img-inline-formula quicklatex-auto-format" alt="F = m\dot{v}" title="Rendered by QuickLaTeX.com" height="12" width="62" style="vertical-align: 0px;" /> <img loading="lazy" src="https://steven.schuerstedt.com/wp-content/ql-cache/quicklatex.com-d6f569502f77616b25335c591893a535_l3.png" class="ql-img-inline-formula quicklatex-auto-format" alt="\dot{x} = v" title="Rendered by QuickLaTeX.com" height="12" width="43" style="vertical-align: 0px;" /> => zwei Gleichungen erster Ordnung DGL erster Ordnung können jetzt einfach in äquivalente Integralgleichungen umgeformt werden, dabei darf natürlich nicht die Integrationskonstante bzw. der Anfangswert vergessen werden. <img loading="lazy" src="https://steven.schuerstedt.com/wp-content/ql-cache/quicklatex.com-18e451e0ea6e5930e520fb225e47420a_l3.png" class="ql-img-inline-formula quicklatex-auto-format" alt="x(t) = x_0 + \int_{t_0}^t v dt" title="Rendered by QuickLaTeX.com" height="26" width="142" style="vertical-align: -8px;" /> <img loading="lazy" src="https://steven.schuerstedt.com/wp-content/ql-cache/quicklatex.com-58bfdd06cb1819258044907915390026_l3.png" class="ql-img-inline-formula quicklatex-auto-format" alt="v(t) = v_0 + \int_{t_0}^t \frac{F}{m}dt" title="Rendered by QuickLaTeX.com" height="26" width="146" style="vertical-align: -8px;" /> Diese beiden Integrale können jetzt numerisch gelöst werden, eine einfache Regel wäre dafür das explizite Euler-Verfahren, was ähnlich zur Riemann Summe ist. Wir zerlegen das Integral in viele kleine Teile die jeweils im Abstand<img loading="lazy" src="https://steven.schuerstedt.com/wp-content/ql-cache/quicklatex.com-14b463d0ecd5b350ced6cf1d6a12eef3_l3.png" class="ql-img-inline-formula quicklatex-auto-format" alt="h" title="Rendered by QuickLaTeX.com" height="12" width="10" style="vertical-align: 0px;" /> voneinander entfernt sind, um nähern das jedes Teilstück mit einem Rechteck an. Alles aufsummiert ergibt dann das Ergebnis. Je kleiner<img loading="lazy" src="https://steven.schuerstedt.com/wp-content/ql-cache/quicklatex.com-14b463d0ecd5b350ced6cf1d6a12eef3_l3.png" class="ql-img-inline-formula quicklatex-auto-format" alt="h" title="Rendered by QuickLaTeX.com" height="12" width="10" style="vertical-align: 0px;" /> ist, desto genauer ist natürlich das Ergebnis. In der Literatur wird das Verfahren immer rekursiv definiert, das mache ich hier genauso, ist auch praktisch für die Implementation. <img loading="lazy" src="https://steven.schuerstedt.com/wp-content/ql-cache/quicklatex.com-98cbaf5f4a8b6a3b0350688b41db01a8_l3.png" class="ql-img-inline-formula quicklatex-auto-format" alt="x_{k+1} = x_k + h v_{k+1}" title="Rendered by QuickLaTeX.com" height="17" width="143" style="vertical-align: -5px;" /> <img loading="lazy" src="https://steven.schuerstedt.com/wp-content/ql-cache/quicklatex.com-45248609503d800bb07a91dd2c7b82ab_l3.png" class="ql-img-inline-formula quicklatex-auto-format" alt="v_{k+1} = v_k + h\frac{F}{m}" title="Rendered by QuickLaTeX.com" height="22" width="122" style="vertical-align: -6px;" /> **=> monte carlo** Ziehe Zufallszahl zwischen Intervallgrenzen und nähere Integral an. Integralgrenzen sind die Startzeit (=0) und die aktuelle gewünschte Zeit. Das erste Integral verweist dann über<img loading="lazy" src="https://steven.schuerstedt.com/wp-content/ql-cache/quicklatex.com-bf6f3f032e9eb6084265f06791454342_l3.png" class="ql-img-inline-formula quicklatex-auto-format" alt="v(t)" title="Rendered by QuickLaTeX.com" height="19" width="28" style="vertical-align: -5px;" /> auf die zweite Gleichung. Wie aber<img loading="lazy" src="https://steven.schuerstedt.com/wp-content/ql-cache/quicklatex.com-9cab50aaa9823eff6906488b66151d85_l3.png" class="ql-img-inline-formula quicklatex-auto-format" alt="F(t)" title="Rendered by QuickLaTeX.com" height="19" width="33" style="vertical-align: -5px;" /> zu einem Zeitpunkt<img loading="lazy" src="https://steven.schuerstedt.com/wp-content/ql-cache/quicklatex.com-b4e3cbf5d4c5c6d9b702dd139f14c147_l3.png" class="ql-img-inline-formula quicklatex-auto-format" alt="t" title="Rendered by QuickLaTeX.com" height="12" width="6" style="vertical-align: 0px;" /> auswerten, wenn<img loading="lazy" src="https://steven.schuerstedt.com/wp-content/ql-cache/quicklatex.com-2510519bbe1660dfdffb4195c7287343_l3.png" class="ql-img-inline-formula quicklatex-auto-format" alt="F" title="Rendered by QuickLaTeX.com" height="12" width="14" style="vertical-align: 0px;" /> mit der Reibung wieder auf<img loading="lazy" src="https://steven.schuerstedt.com/wp-content/ql-cache/quicklatex.com-6bc6064f1ddc8d661f00698f562b4616_l3.png" class="ql-img-inline-formula quicklatex-auto-format" alt="\dot{x}" title="Rendered by QuickLaTeX.com" height="12" width="10" style="vertical-align: 0px;" /> verweist? #### Schiefer Wurf als Zwei-Körperproblem Eine weitere mögliche Erweiterung ist es den schiefen Wurf als Zwei-Körper Problem zu betrachten. Nach unseren Vorstellungen der Physik wirkt die Gravitation in beide Richtungen, d.h. unser Wurfgeschoss wird von der Erde (oder einen anderen Planeten) angezogen, aber genauso wird auch die Erde von unseren Wurfgeschoss angezogen. Natürlich unterscheiden sich die beiden Massen enorm, wodurch dieser Effekt kaum zum Tragen kommt. Wenn man diese beidseitige Anziehung als Differenzialgleichungen formuliert und auflöst, kommt man zu den Keplerbahnen, welche eine Ellipse darstellen. Kepler hatte dieses Problem bei der Gravitation von Planeten untereinander untersucht, hier sind die Massen natürlich wesentlich näher zusammen. Genau genommen ist ein Zwei-Körperproblem immer noch zu eng gefasst, unser Wurfgeschoss wird ja eigentlich nicht nur von der Erde angezogen, sondern auch von der Sonne (und allen anderen Objekten im Universum, die Gravitation hört laut Theorie nie auf). Doch beim Drei-Körper-Problem gibt es schon keine Lösung mehr der Differentialgleichungen, und das ganze verfällt schnell in ein chaotisches System. #### Jetzt wird gependelt Das Fadenpendel, zum Einstieg wieder mit einfacher Gewichtskraft und mit ohne Reibung. Auf die Masser wirkt wieder die Gewichtskraft, aber durch den Faden wird ein Teil der Gewichtskraft durch die Gegenkraft des Fadens kompensiert. Wenn wir den Kraftvektor der Gewichtskraft in einen Radial und einen Tangentialteil aufteilen, dann wird der Radialteil vollständig vom Faden kompensiert und nur die Tangentialekraft spielt für die Bewegung eine Rolle. Hier eignen sich nun Polarkoordinaten, da dann eine Koordinate eleminiert werden kann. (genau die Radiale eben) $$ x = r \cos{\theta}$$ $$ y = r \ sin{\theta}$$ Mit der neuen Koordinate `$\theta$` können wir jetzt die Bewegungsgleichung mit der Tangentialkraft formulieren. $$ \ddot{\theta} = - \frac{g}{l} \sin{\theta} $$ Wobei `$l$` die Länge des Fadens ist. Für kleine Winkel kann der sinus als gute Annäherung weggelassen werden und die dann einfachere Gleichung kann mit einem Exponential Ansatz oder den sinus/cosinus Funktionen gelöst werden. So wie die Gleichung eigentlich lautet führt die Lösung auf elliptische Integrale, die dann keine explizite Lösung haben, sondern sich z.B. als unendlich Reihe annähern lassen. $$ \theta = \theta_0 \cos{\frac{g}{l} t} $$ Diese Gleichung kann jetzt als Pendelsimulation verwendet werden, aber natürlich muss die Koordinate `$\theta$` noch in die Koordinaten x und y zurücktransformiert werden, wie oben beschrieben, da ja unser Bildschirm rechteckig ist und somit letztlich nur kartesische Koordinaten versteht. Lagrange-Mechanik (Pendel, beispiel für Schiefer Wurf?) => keine Reibung mit Lagrange (Was ist Reibung?) Finde Bewegungsgleichungen mit Lagrange-Ansatz und füge dann Reibungskräfte hinzu.

177.818182

1,787

0.727387

deu_Latn

0.729603

e97363957d08806218a88edf725864a14b0776a7

11,697

md

Markdown

scalingbitcoin/tel-aviv-2019/scriptless-lotteries.md

stickies-v/bitcointranscripts

f1ababde20a00058c3dc78ca6954c83b4413ebee

[ "MIT" ]

51

2021-03-31T14:10:50.000Z

2022-03-25T10:05:55.000Z

scalingbitcoin/tel-aviv-2019/scriptless-lotteries.md

stickies-v/bitcointranscripts

f1ababde20a00058c3dc78ca6954c83b4413ebee

[ "MIT" ]

57

2021-03-30T21:25:16.000Z

2022-03-31T13:54:53.000Z

scalingbitcoin/tel-aviv-2019/scriptless-lotteries.md

stickies-v/bitcointranscripts

f1ababde20a00058c3dc78ca6954c83b4413ebee

[ "MIT" ]

27

2021-03-19T11:02:03.000Z

2022-03-21T01:29:38.000Z

--- title: Scriptless Lotteries transcript_by: Bryan Bishop categories: ['conference'] tags: ['cryptography'] --- Scriptless lotteries on bitcoin from oblivious transfer Lloyd Fournier (lloyd.fourn@gmail.com) <https://twitter.com/kanzure/status/1171717583629934593> # Introduction I have no affiliations. I'm just some guy. You're trusting a guy to talk about cryptography who got the date wrong. We're doing scriptless bitcoin lotteries from oblivious transfer. # Lotteries Imagine a trusted party who conducts lotteries between Alice and Bob. The goal of the lottery protocol is to use a cryptographic protocol without having a lottery trusted party. The idea is that the honest parties have a 1/n chance of winning each time. # Scriptless Bitcoin has a way of specifying spending rules on coins. We use a cryptographic protocol to realize the conditions under which the coins can be spent. The conditions can be spent, and somehow the person will be able to magically arrive at a signature. You can use instead of OP\_CHECKMULTISIG a threshold multisig scheme, or you can replace HTLC by using "adaptor" signatures. These two things, you can pretty much replace most of the useful stuff you can do with bitcoin script. I think you can do almost all of lightning, but Andrew who came up with adaptor signatures said no you can't-- timelocks maybe. Scriptless is interesting because they are more efficient and more private. Also, it's interesting to know what w ecan do and can't be done without script. What do you really need scripts and opcodes for? <https://bitcointalk.org/index.php?topic=355174.0> "..I think the multi-party lotter y scheme still rates as the most advanced usage of script yet found in the wild." - mike hearn, this was before lightning but it's still up there. So what we will be doing today is showing a lottery that doesn't use a script at all. # Lottery without a trusted third party You need to fairly generate randomness, no OP\_RANDOM, you need a few other requirements that I am going to skip over apparently. # Coin tossing There was a seminal paper in 1981 called "Coin flipping by telephone" but people quickly called it coin tossing instead or something. This was Manuel Blum in 1981. Alice sends a commitment to a coin toss to Bob, Bob sends his coin toss back, Bob checks Alice's result against the commitment. The result is computed against both coin tosses. # Hash-commitment coin tossing Here is how the bitcoin version works. Alice chooses a random bit, and she commits to it with a hash function with a long random string or nonce. Bob sends his value, and Alice sends the value. Hopefully, no party aborts. The thing to make note of is that you can get Alice, she learns the output first. There's no way to solve this problem, but you can sprinkle some blockchain to solve some problem, but generally Alice always learns the value first. She might not release the preimage to tell Bob that she lost. So a lottery protocol has to overcome this. # First attempt at lottery protocols <https://bitcointalk.org/index.php?topic=277048.0> Many of the original protocols use collaterla to force both parties to reveal pre-images. Adam Back came up with a more appropriate idea, which is that if some party doesn't do something at some point, then they just lose all the money instead. # Miller-Bentov 2016 There were quite a few academic papers after that thread, like 4-6 papers or something. There was one that succinctly summarized the idea with the "Zero-collateral lotteries in bitcoin and ethereum" paper. So you both have a fund transaction, you sign into it, but you already have transactions spending from it before you put it on the blockchain. Each transaction acts like a state. The funding goes down; Alice can move it to the next state by revealing her preimage, and then-- so she already has that transaction signed, she needs the value to go to the next state, and then in the next state, Bob can take the money if he reveals a value such that his value and Alice's value can do something interesting. Otherwise, he can't do anything except wait for a timeout where Alice gets the money. There's no collateral in this. It's what we want. The winner just takes out the bitcoin with probability 1/2. This is probably the simplest hash-commitment lottery protocol. What you can see is that you got these hash preimage reveals, but if we want to make this scriptless; we can replace HTLCs with adaptor signatures normally, but in this case we can't because you're revealing the preimages but you're actually spending the money on a function of the two preimages. It's some predicate on the two preimages determines whether it can be spent, it's two preimages and a predicate. It's a non-trivial use of script, it's interesting that we can do this without any script at all. # Scriptless lottery through oblivious transfer We want Alice and Bob to pay into a funding setup transaction, and then we want no script used at all to do this. We're going to change the cryptographic primitive to oblivious transfer instead of coin tossing. Manuel Blum also came up with this idea in 1981. He came up with two ideas for doing random bits. He did coin tossing, and also oblivious transfer. Oblivious transfer is where Alice transmits 1 of n messages to Bob of Bob's choosing but Alice doesn't learn which one that Alice transmitted. The sender doesn't know which message was sent. The receiver only gets one of the messages. Alice has n messages, Bob chooses one that he wants to learn, Alice doesn't learn which one he learns. That's the basic idea. You can get a random bit from that. Bob chooses a random bit, Alice chooses a random message, and Bob learns the message according to his bit. He learns the result after Alice sends her bit over, he sends the message he learns back to Alice, and Alice looks and sees hwich message did he choose to learn, and then she picks based on that. # Oblivious signing It might not be clear how to go from that to some kind of bitcoin protocol. We're going to do oblivious transfer of signatures. It's not just "messages" arbitrary. It's not quite obvivious transfer, though. If we replaced the messages with just signatures, what would happen is that Alice could just put one message as a signature and the other one is just garbage and then Bob does oblivious transfer and he gets the signature and he thinks everything is fair but Alice knows which message he got because the garbage was the other one. So we have to have some verifiable oblivious transfer, called oblivious signing. Bob chooses which message he wants signed, and Alice doesn't know which one was signed. We're going to use oblivious signing. We have a fund transaction that we sign last, and we first sign the child transactions. By the way, this is all predicated on having Schnorr signatures and you could probably do it with ECDSA but that's not this talk. You have to sign the transaction scaffold after you choose the key securely. You have to sign all the abort transactions and the lottery winning transactions. For the Bob wins transactions, you have to do oblivious signing, at Bob's choosing, but Alice doesn't know which one he chose her to sign. Then you sign the transactions to fund. Also, these transactions have timeouts where the other party wins. If you have a secure oblivious signing protocol, then each party would win 50% of the time here. So the only options are either Alice wins and Bob timeout loses, or Bob wins and Alice timeout loses or something. # Adaptor signatures (Poelstra 2017) I am sure you have seen these before. Here they are in multiplicative notation instead. You have an auxiliary point, this conditional point that you add to the signing algorithm. You multiply the nonce value by this. The s value you get out of the signature is missing the discrete log of the condition. There's Y condition and y the satisfaction of the condition. An important feature is that the signer learns little y once they see the signature. So then you learn little y when you see the signature on the blockchain. # Oblivious signing again Alice to give Bob adaptor signatures where Bob only knows the completion for one of them. We need Bob to know a discrete log of some point but only one of some set of points. So a pedersen commitment is given of a certain form; it's impossible to decommit to more than one value without knowing the discrete log of some h with respect to g. If we can instead fix C to 0 or 1, then the committer can only know the discrete log of T or TH^(-1). They can only know the discrete log of one of those two. To put these two ideas together, the idea is that you can only know the decommitment for one pedersen commitment, and adaptor signatures. Bob has a choice, 0 or 1, he generates a random y value, and--- Alice creates two adaptor signatures, one on T and one on TH^(-1) and then sends them over to Bob. He has to verify both of them, that they are all valid adaptor signatures. He verifies both of them, and then he completes one. That's it, that's how we get oblivious signing. # Security Security for the sender is that if Bob completes both adaptor signatures, saying that he reveals the completion, or revealing the discrete log of the condition, then we're going to learn the discrete log of T and TH^(-1) which Bob learns-- so the discrete log.. violates that the discrete log is hard, so Alice has that security in that respect. It's information theoretically impossible for Alice to learn which choice Bob made, it's indistinguishable from random. I came up with that, I was very happy with myself. I don't invent cryptographic primitives very often. I decided to call it "oblivious signing" and then I googled it and found out that someone else already wrote it up, in 2008 (2006?). # Two-party oblivious signing Not so fast! our transaction outputs are locked by joint public keys. Both Alice and Bob have half the public key, so we can't just use that algorithm by itself, we have to change it a bit. I think these changes preserve the security from the slide before. They both choose joint nonces, we did this already. Along with T, Bob sends his half adaptor signatures for m0 (BobWin0) and m1 (BobWin1) under B0 and B1. Alice calculates the full adaptor signatures and sends them back to Bob. So we've managed to do two party on the joint public keys. That's it, we did it. Just to recap on this, so now Alice posts the fund transaction, she picks one or picks zero, Bob now if he chose the same bit as Alice he is able to take the money, and otherwise Alice takes it. With 50/50 probability, Alice is going to win the lottery. # Summary Lotteries were previously an eample of something that could only be done with non-trivial scripts. But they can actually be done without script, and actually they can be done efficiently without script and still on-chain. Obvliious signing with Schnorr signatures is secure and efficient (at least as it is used here). Some unsubstantiated claims: you can do lotteries with different odds by doing 1/N oblivious signing rathe rthan 1/2. You can cooperatively complete the lottery in two on-chain transactions. I think you can execute the cooperative protocol in a payment channel, where it's a UTXO in a state of a payment channel, and even do it in a "multi-hop" but that's conjecture. There can be a guy in the middle who has a lottery on his left hand side and a lottery on the right hand side, and he's guaranteed to lose one and win the other and he doesn't know which one and he will be a man in the middle, and you can do that recursively so you can do many hops of that.

108.305556

960

0.78798

eng_Latn

0.999868

e9736b34c3b66ba9ba1be479c1aa1fae07267a66

42

md

Markdown

README.md

DeniKucevic/Forum-FullStack

e2c57d69ede16ea0ceb03330accbdde2a3b549e0

[ "MIT" ]

null

README.md

DeniKucevic/Forum-FullStack

e2c57d69ede16ea0ceb03330accbdde2a3b549e0

[ "MIT" ]

null

README.md

DeniKucevic/Forum-FullStack

e2c57d69ede16ea0ceb03330accbdde2a3b549e0

[ "MIT" ]

null

# Forum-FullStack Fullstack forum project

14

23

0.833333

eng_Latn

0.608922

e9751849db1f21833617902dea082462b2b2cd2d

1,635

md

Markdown

README.md

hectorqin/mcrypt

fb55514e5336680c01a0ec880cd79cf2c1b301bc

[ "MIT" ]

1

2020-06-08T02:38:55.000Z

README.md

hectorqin/mcrypt

fb55514e5336680c01a0ec880cd79cf2c1b301bc

[ "MIT" ]

null

README.md

hectorqin/mcrypt

fb55514e5336680c01a0ec880cd79cf2c1b301bc

[ "MIT" ]

null

# mcrypt A simple class for performing AES encryption with mcrypt. In general, support all module and mode of the mcrypt extension. ## Usage ``` require_once 'Mcrypt.php'; $string = 'test'; $key = '1234567812345678'; // AES/ECB/PKCS5Padding Mcrypt::setMode(MCRYPT_RIJNDAEL_128, MCRYPT_MODE_ECB, Mcrypt::PKCS5); $encryptedString = Mcrypt::encrypt($string, $key); $decryptedString = Mcrypt::decrypt($encryptedString, $key); echo $string, " ", $encryptedString, " ", $decryptedString, "\n"; // AES/ECB/PKCS7Padding Mcrypt::setMode(MCRYPT_RIJNDAEL_128, MCRYPT_MODE_ECB, Mcrypt::PKCS7); $encryptedString = Mcrypt::encrypt($string, $key); $decryptedString = Mcrypt::decrypt($encryptedString, $key); echo $string, " ", $encryptedString, " ", $decryptedString, "\n"; // AES/ECB/ZEROPadding Mcrypt::setMode(MCRYPT_RIJNDAEL_128, MCRYPT_MODE_ECB, Mcrypt::ZERO); $encryptedString = Mcrypt::encrypt($string, $key); $decryptedString = Mcrypt::decrypt($encryptedString, $key); echo $string, " ", $encryptedString, " ", $decryptedString, "\n"; // AES/ECB/ISO10126Padding Mcrypt::setMode(MCRYPT_RIJNDAEL_128, MCRYPT_MODE_ECB, Mcrypt::ISO10126); $encryptedString = Mcrypt::encrypt($string, $key); $decryptedString = Mcrypt::decrypt($encryptedString, $key); echo $string, " ", $encryptedString, " ", $decryptedString, "\n"; // AES/ECB/ANSIX923Padding Mcrypt::setMode(MCRYPT_RIJNDAEL_128, MCRYPT_MODE_ECB, Mcrypt::ANSIX923); $encryptedString = Mcrypt::encrypt($string, $key); $decryptedString = Mcrypt::decrypt($encryptedString, $key); echo $string, " ", $encryptedString, " ", $decryptedString, "\n"; ``` ## LICENSE MIT

32.058824

72

0.722324

yue_Hant

0.267091

e975fbc4cdd9bd302058d295e3fc087bdaf5c907

3,737

md

Markdown

treebanks/en_gum/en_gum-dep-aux-pass.md

sylvainkahane/docs

50340ae2af8009c020a3d048ddc40c593a44d268

[ "Apache-2.0" ]

null

treebanks/en_gum/en_gum-dep-aux-pass.md

sylvainkahane/docs

50340ae2af8009c020a3d048ddc40c593a44d268

[ "Apache-2.0" ]

null

treebanks/en_gum/en_gum-dep-aux-pass.md

sylvainkahane/docs

50340ae2af8009c020a3d048ddc40c593a44d268

[ "Apache-2.0" ]

null

--- layout: base title: 'Statistics of aux:pass in UD_English-GUM' udver: '2' --- ## Treebank Statistics: UD_English-GUM: Relations: `aux:pass` This relation is a language-specific subtype of <tt><a href="en_gum-dep-aux.html">aux</a></tt>. 678 nodes (1%) are attached to their parents as `aux:pass`. 677 instances of `aux:pass` (100%) are right-to-left (child precedes parent). Average distance between parent and child is 1.24778761061947. The following 3 pairs of parts of speech are connected with `aux:pass`: <tt><a href="en_gum-pos-VERB.html">VERB</a></tt>-<tt><a href="en_gum-pos-AUX.html">AUX</a></tt> (672; 99% instances), <tt><a href="en_gum-pos-ADJ.html">ADJ</a></tt>-<tt><a href="en_gum-pos-AUX.html">AUX</a></tt> (5; 1% instances), <tt><a href="en_gum-pos-NOUN.html">NOUN</a></tt>-<tt><a href="en_gum-pos-AUX.html">AUX</a></tt> (1; 0% instances). ~~~ conllu # visual-style 2 bgColor:blue # visual-style 2 fgColor:white # visual-style 3 bgColor:blue # visual-style 3 fgColor:white # visual-style 3 2 aux:pass color:blue 1 They they PRON PRP Case=Nom|Number=Plur|Person=3|PronType=Prs 3 nsubj:pass _ _ 2 were be AUX VBD Mood=Ind|Tense=Past|VerbForm=Fin 3 aux:pass _ _ 3 sold sell VERB VBN Tense=Past|VerbForm=Part 0 root _ _ 4 at at ADP IN _ 7 case _ _ 5 eighth-grade eighth-grade NOUN NN Number=Sing 7 compound _ _ 6 basketball basketball NOUN NN Number=Sing 7 compound _ _ 7 games game NOUN NNS Number=Plur 3 obl _ _ 8 on on ADP IN _ 10 case _ _ 9 Friday Friday PROPN NNP Number=Sing 10 compound _ _ 10 nights night NOUN NNS Number=Plur 7 nmod _ SpaceAfter=No 11 . . PUNCT . _ 3 punct _ _ ~~~ ~~~ conllu # visual-style 2 bgColor:blue # visual-style 2 fgColor:white # visual-style 3 bgColor:blue # visual-style 3 fgColor:white # visual-style 3 2 aux:pass color:blue 1 She she PRON PRP Case=Nom|Gender=Fem|Number=Sing|Person=3|PronType=Prs 3 nsubj _ _ 2 was be AUX VBD Mood=Ind|Number=Sing|Person=3|Tense=Past|VerbForm=Fin 3 aux:pass _ _ 3 staggered staggered ADJ JJ Degree=Pos 0 root _ _ 4 by by ADP IN _ 6 case _ _ 5 the the DET DT Definite=Def|PronType=Art 6 det _ _ 6 loss loss NOUN NN Number=Sing 3 obl _ _ 7 last last ADJ JJ Degree=Pos 8 amod _ _ 8 year year NOUN NN Number=Sing 6 nmod:tmod _ _ 9 to to ADP TO _ 11 case _ _ 10 the the DET DT Definite=Def|PronType=Art 11 det _ _ 11 Cardinals cardinal PROPN NNPS Number=Plur 6 nmod _ SpaceAfter=No 12 . . PUNCT . _ 3 punct _ _ ~~~ ~~~ conllu # visual-style 13 bgColor:blue # visual-style 13 fgColor:white # visual-style 15 bgColor:blue # visual-style 15 fgColor:white # visual-style 15 13 aux:pass color:blue 1 Biologists biologist NOUN NNS Number=Plur 2 nsubj _ _ 2 think think VERB VBP Mood=Ind|Tense=Pres|VerbForm=Fin 0 root _ _ 3 that that SCONJ IN _ 5 mark _ _ 4 fear fear NOUN NN Number=Sing 5 nsubj _ _ 5 causes cause VERB VBZ Mood=Ind|Number=Sing|Person=3|Tense=Pres|VerbForm=Fin 2 ccomp _ _ 6 this this DET DT Number=Sing|PronType=Dem 8 det _ _ 7 " " PUNCT `` _ 8 punct _ SpaceAfter=No 8 hypnosis hypnosis NOUN NN Number=Sing 5 obj _ SpaceAfter=No 9 , , PUNCT , _ 8 punct _ SpaceAfter=No 10 " " PUNCT '' _ 8 punct _ _ 11 which which PRON WDT PronType=Rel 15 nsubj _ _ 12 may may AUX MD VerbForm=Fin 15 aux _ _ 13 be be AUX VB VerbForm=Inf 15 aux:pass _ _ 14 an an DET DT Definite=Ind|PronType=Art 15 det _ _ 15 attempt attempt NOUN NN Number=Sing 8 acl:relcl _ _ 16 to to PART TO _ 18 mark _ _ 17 " " PUNCT `` _ 18 punct _ SpaceAfter=No 18 play play VERB VB VerbForm=Inf 15 xcomp _ _ 19 dead dead ADJ JJ Degree=Pos 18 xcomp _ SpaceAfter=No 20 " " PUNCT '' _ 18 punct _ _ 21 to to PART TO _ 22 mark _ _ 22 fool fool VERB VB VerbForm=Inf 15 acl _ _ 23 predators predator NOUN NNS Number=Plur 22 obj _ SpaceAfter=No 24 . . PUNCT . _ 2 punct _ _ ~~~

38.927083

417

0.727857

yue_Hant

0.573099

e9765615525de3b9189c3005c1c1cdd88891a370

58

md

Markdown

README.md

lookyhooky/wasd

33329e30e7d02d9d9ba1473f6891f4aa72573a1c

[ "MIT" ]

null

README.md

lookyhooky/wasd

33329e30e7d02d9d9ba1473f6891f4aa72573a1c

[ "MIT" ]

null

README.md

lookyhooky/wasd

33329e30e7d02d9d9ba1473f6891f4aa72573a1c

[ "MIT" ]

null

# WASD A terminal emulator for text based browser games.

14.5

49

0.775862

eng_Latn

0.980485

e976a662dbe2e1b398f45e279955afe90ec9ecee

2,146

md

Markdown

desktop-src/Controls/lvn-getemptymarkup.md

KrupalJoshi/win32

f5099e1e3e455bb162771d80b0ba762ee5c974ec

[ "CC-BY-4.0", "MIT" ]

null

desktop-src/Controls/lvn-getemptymarkup.md

KrupalJoshi/win32

f5099e1e3e455bb162771d80b0ba762ee5c974ec

[ "CC-BY-4.0", "MIT" ]

null

desktop-src/Controls/lvn-getemptymarkup.md

KrupalJoshi/win32

f5099e1e3e455bb162771d80b0ba762ee5c974ec

[ "CC-BY-4.0", "MIT" ]

null

--- title: LVN_GETEMPTYMARKUP notification code description: Sent by list-view control to its parent window when the control has no items. The LVN\_GETEMPTYMARKUP notification code is a request for the parent window to provide markup text. This notification code is sent in the form of a WM\_NOTIFY message. ms.assetid: 5ea74120-f347-493a-af14-6bda5b8f6082 keywords: - LVN_GETEMPTYMARKUP notification code Windows Controls topic_type: - apiref api_name: - LVN_GETEMPTYMARKUP api_location: - Commctrl.h api_type: - HeaderDef ms.topic: reference ms.date: 05/31/2018 --- # LVN\_GETEMPTYMARKUP notification code Sent by list-view control to its parent window when the control has no items. The LVN\_GETEMPTYMARKUP notification code is a request for the parent window to provide markup text. This notification code is sent in the form of a [**WM\_NOTIFY**](wm-notify.md) message. ```C++ LVN_GETEMPTYMARKUP pnmMarkup = (NMLVEMPTYMARKUP*) lParam; ``` ## Parameters <dl> <dt> *lParam* </dt> <dd> Pointer to a [**NMLVEMPTYMARKUP**](/windows/win32/api/commctrl/ns-commctrl-nmlvemptymarkup) structure. Set the members of this structure to provide markup text for the list-view control. </dd> </dl> ## Return value Return **TRUE** to set the markup text in the list-view control, or **FALSE** otherwise. ## Remarks The notification receiver casts *lParam* to retrieve the [**NMLVEMPTYMARKUP**](/windows/win32/api/commctrl/ns-commctrl-nmlvemptymarkup) structure. The *wParam* parameter contains the ID of the control that sends this message. ## Requirements | | | |-------------------------------------|---------------------------------------------------------------------------------------| | Minimum supported client<br/> | Windows Vista \[desktop apps only\]<br/> | | Minimum supported server<br/> | Windows Server 2008 \[desktop apps only\]<br/> | | Header<br/> | <dl> <dt>Commctrl.h</dt> </dl> |

30.225352

266

0.624884

eng_Latn

0.80723

e976eb1a77b73742ea2a2ef8929fb6804da22504

79

md

Markdown

README.md

mattbrowley/LightSims

289af58d1fb622c543a6d3c3cec752e654309ff2

[ "MIT" ]

null

README.md

mattbrowley/LightSims

289af58d1fb622c543a6d3c3cec752e654309ff2

[ "MIT" ]

null

README.md

mattbrowley/LightSims

289af58d1fb622c543a6d3c3cec752e654309ff2

[ "MIT" ]

null

# LightSims Python simulations of interesting light and light/matter phenomena

26.333333

66

0.848101

eng_Latn

0.986855

e977564eb59b798b19534b6f01bfe0140a4b1844

691

md

Markdown

README.md

tmforum-apis/TMF664_ResourceFunctionActivationConfiguration

fddc2823e1b02e795dc3d3e9ea960341e2f0d7d8

[ "Apache-2.0" ]

null

README.md

tmforum-apis/TMF664_ResourceFunctionActivationConfiguration

fddc2823e1b02e795dc3d3e9ea960341e2f0d7d8

[ "Apache-2.0" ]

null

README.md

tmforum-apis/TMF664_ResourceFunctionActivationConfiguration

fddc2823e1b02e795dc3d3e9ea960341e2f0d7d8

[ "Apache-2.0" ]

1

2020-11-10T19:43:30.000Z

# TMF664_ResourceFunctionActivationConfiguration TM Forum Open APIs (Apache 2.0) Resource Function Activation and Configuration API This API introduces Resource Function which is used to represent a Network Service as well as a Network Function. The Network Service and Network Function class definitions and associations in TR244 (which, in turn, builds on concepts from the SID addenda on Logical Resource and Service) are utilized to define the Resource Function. To access this API; (the Specification, Postman Collection, Swagger file, Reference Implementation, Conformance Profile, and CTK) go to the Open API table at: https://projects.tmforum.org/wiki/display/API/Open+API+Table

53.153846

89

0.819103

eng_Latn

0.642929

e977f0f14bf8c5029cc67654ab1842f323932f8d

12,252

md

Markdown

_posts/2016-01-26-data-inputs-and-editing.md

lassegs/skole

c30fae8436092f710e98bcf7a957032df84a7e00

[ "MIT" ]

null

_posts/2016-01-26-data-inputs-and-editing.md

lassegs/skole

c30fae8436092f710e98bcf7a957032df84a7e00

[ "MIT" ]

null

_posts/2016-01-26-data-inputs-and-editing.md

lassegs/skole

c30fae8436092f710e98bcf7a957032df84a7e00

[ "MIT" ]

null

--- id: 482 title: Data inputs and editing date: 2016-01-26T12:05:41+00:00 author: lassegs layout: post guid: http://skole.lassegs.org/?p=482 permalink: /2016/01/26/data-inputs-and-editing/ categories: - SGO4940 --- <div> <em>Andreas Forø Tollefsen,</em> </div> <div> </div> <div> <strong>Slides from last lecture:</strong> </div> <div> </div> <div> Represent elevation: Elevation as contour lines. ISOlines, equidistance is the distance from one line to next. </div> <div> Elevation as polygons. Also generalizing, classifying heights into groups. </div> <div> Elevation as raster. Continous data scale. Gives better approximation of the heights between classes. </div> <div> Elevation as TIN: Triangulated Irregular Netwrk. Direction and ascpect is non varying within triangles. </div> <div> </div> <div> Raster – 3D models- Continious data. Representing frequency as elevation. Useful for some purposes. </div> <div> </div> ### Generalization of reality <div> We always have generalizations of the real world. We cannot make perfect models of something as complex. So we make generalizations, we ignore differences and set borders </div> <div> </div> ### Think about similarities <div> Similarities in locations and similarities in attributes. Spatial autocorrelation is more complex than </div> <div> Positive Serial Correlation. Similarities in time, all the data points are dependent on the previous point in time. The values and the timing of the point follows each other. This is prevalent. </div> <div> Negative Serial Correlation is not very common. </div> <div> </div> <div> Spatial autocorrelation is similarities across space. Many directions simultaneously. Recap Tobler’s first law of geography! </div> <div> <em>«Everything is related to everything else, but near things are more related than distant things.» </em>Tobler. </div> <div> </div> <div> Spatial heterogeneity: Locations are different </div> <div> Spatial homogeneity: Locations are similar </div> <div> Similarity where? DIstance and scope affects similarity. </div> <div> </div> ### Smoothness / irregularity ### Spatial autocorrelation <div> Similar to Toblers first law: Positive spatial autocorrelation: Similitarity in both position and attributes. </div> <div> Opposite to Tobler’s first law: Negative spatial autocorrelation. Similarity in position, but not in attributes. </div> <div> Zero autocorrelation when position and attributes are completely independent. No pattern, random. </div> <div> </div> <div> The most used way to measure this is Morans I. A measure of the spatial autocorrelation from -1 to +1. 0 is random, no pattern. </div> <div> -1 is perfect negative spatial autocorrelation. We cannot reach perfect positive autocorrelation. </div> ### Morans I <div> Both vector and raster data. The most used indicator for spatial autocorrelation. </div> <div> </div> ### Dissimilarity <div> Is likely to occur when competition between regions or actors outweigh cooperative factors. </div> ### Sampling methods <div> Random selection – most used. Throw out points in an area. </div> <div> Stratified selection – make a grid, do selections in the intersections </div> <div> Stratified random selection – </div> <div> Stratified selection with random grid variations – random grid size, measuer in intersections </div> <div> Cluster selections – </div> <div> Cross sectional selection </div> <div> Contour line selection </div> <div> </div> ### Spatial data input and editing <div> Geo-referencing. What should we attach data to? Coordinate systems. Lengths and latitude. Datum. Projections. Primary and secondary data sources. </div> <div> </div> <div> Goodchild 2011 three meanings of scale. Representative fraction. Exxtent in space. Resolution. </div> <div> Bott and Young. The role of crowd-sourcing. Open-source data and information. Increase collective knowledge, community building, collective creativity and innovation, crowdfunding, civic engagement. Crowdsourcing GIS and community knowledge important, like environmental management, crisis management, post-conflict. More on this in the Qualitative GIS lecture. </div> <div> </div> ### Geo-referencing <div> Several terms are used interchangeably: mapping, tagging, geo-coding. Geo-referncing in this regard: link an object or attribute to a location (possibly also to some point), placing the object or attribute geographically. </div> ### What should we attach data to? <div> The main requirement for localization is that the geographical reference is </div> * – Unique, so taht there is only one location which corresponds to the reference. * The existence of a common understanding to contents of the refrence ssytem that is shared. * A stable reference system. <div> In our use of GIS we link data either <strong>explicitly</strong> to the coordinates (latitude and longitude, X and Y) or <strong> implisityly </strong>assumed for the references we use, such as place, administrative zones, regions, addresses. </div> <div> </div> <div> Take into account double phenomena (cities called Springfield), addresses and change of names. </div> <div> Residential adresses is a good way to locate housing and economic activity in cities and towns, but does not work so well in rural areas. </div> <div> </div> ### Geographic coordinate systems <div> The safest way to localize. Only one unique coordinate for each location. Persistent through time. Common understanding fo the system. </div> <div> Latitude (paralell with equator] Based on the equator ( a sectional earth perpendicular to the rotation axis and the mass mean point. Ranges from 90 degress south to 90 degrees north. </div> <div> Longitude. Based on the 0 meridian through Greenwich observatory. Ranges from 0 – 180 east and 0 – 180 west. </div> <div> </div> <div> We typically convert coordinates to desmal degrees. Decimal degrees = (degrees + Minutes / 60) + (Seconds / 3600). </div> <div> </div> <div> Earth is not a perfect sphere. </div> <div> Global Datum WGS84 is the best fit globally. </div> <div> Local Datum (best fit for local area of interest). </div> <div> </div> <div> We need datum to establish reference systems on the earths surface. Euref89 is Norwegian. </div> <div> We are projecting coordinates of the ellipsoid on to flat maps. Different projections take different characteristics. </div> <div> Equal area: Area correct </div> <div> Conform: The shape of areas corret </div> <div> Equidistant: Measurd distance correct. </div> <div> Retroazimuthal: Measured directions are correct. </div> <div> Compromise: No specific properties are correct. Minimize all errors. </div> <div> </div> ### Common projections <div> Planar: We imagine taht we put a flat sheet to the world. The representation is appropriate touch point. This is often used on the map of the polar regions. </div> <div> Cylinder projection: Stretch a sheet around the globe. the representation is correct along the touch line. </div> <div> Conic projection: Will most correct along a latitude between the equator and the pole, depending on the cone shape. </div> <div> Projections may be either tangent (the sheet touches the globe) or Secant (the sheet cuts through the globe, so we get two touch lines). </div> <div> </div> ### Plate Caree (cylindrical equidistant projection): <div> The simplest form of projection: latitude as the x-coordinates and longitude as y-coordinates. Distances are right on the equator and along the meridians, but not otherwise. </div> <div> The cartesian coordinate system. </div> <div> Universal Transverse Mercator (UTM) projection, map wrappped around the globe, but over the transverse. UTM parts globe in 60 different zones, each 6 degrees wide. </div> <div> Norway is covered byt the UTM zone 31N – 36N, but it is common to use zone 33N throughout Norway. UTM is all in meters, good for measuring distances. </div> ### Why is this important? <div> Because if we read into different layers with different datum, geographic coordinate systems and projections, we cannot match the layers to each other and we will not be able to analyze various data layers against each other. </div> <div> </div> <div> We can show degrees of error in maps with Tissot matrix. </div> <div> </div> ### Data models in GIS <div> Representation and data model are overlapping concepts. </div> * Representation is more conceptual and scientific * Data models used moer in practice and in database and project design <div> How the geographical reality is modeled in a GIS? </div> <div> </div> <div> A data model is a set of constructs for describing and representing part of the real world in a computer. </div> <div> </div> <div> A data model defines the data structure and determines how data is stored and therefore consequently affect the types of analysis taht can be performed. It is a simplified description of reality. </div> <div> </div> <div> We go from the real world. We make the data model, describe and represent. Operational analysis and presentation. People . </div> ### Levels of generalization or simplification. <div> Conceptual model: reality -> Conceptual -> logical model – physical model. </div> <div> Reality includes everything. Comprised of real phenomena. Buildings, roads, wells, lakes, people, etc. Need to simplify. We have to generalize reality into a manageable form. </div> <div> Abstraction level – conceptual. Human oriented. Partly structured model with selected objects and processes. Which objets and processes are relevant for our purpose+ </div> <div> Logical model implementation oriented. </div> <div> Physical model. The actual implementation in GIS. Tables stored as files or databases. Digital terms. </div> <div> </div> <div> Computer models as common framework. Important that everyone has a common understanding of the project. </div> <div> From system design to system. Describes project in-depth. Document how you gather data, from systems design to the system itself. </div> <div> </div> <div> In ArcGIS we have the model builder. It takes input, shows tools we need to get a certain output. </div> <div> GIS data model types are based on continuous fields and discrete objects. GIS data models are based on layers. </div> <div> </div> <div> Raster data model consists of strict matrix of cells or pixels to represent real objects. One value per pixel. Can be compressed. Satellite Images can have multiple raster bands. hus one color value per band can be assigned. For example, saturation values of respectively red, green and blue can be combined to visualize teh sattelite data. We cannot add variables to the pixels. </div> <div> A raster often contain header / metadata. </div> <div> The coordinates of starting corner. </div> <div> Pixel size (cell size) </div> <div> Number of rows and columsn. </div> <div> The projection. </div> <div> No-data value. </div> <div> </div> ### Vector model <div> Simple features. point line or polygon </div> <div> Topological features. The science and mathematics in vector data. This information can be used for network analysis to test the validity of a polygon adjacency or other topological errors. Network connectivity. </div> <div> </div> <div> Data collection: </div> <div> Planning – preperation – digitizing, transfering – editing, improving – evaluation. And go again. </div> <div> </div> ### Collecting data <div> Primary data sources: Collected in digital format for a particular GIS project. </div> <div> Two broad categories of data sources: </div> * Data collection (direct collection): Primary sources. Secondary sources. * Data transfer (exchange of collected data) <div> Data collection is often time consuming and expensive </div> <div> </div>

23.929688

382

0.731146

eng_Latn

0.991571

e9783cb1d6a0486e9ff46fc5c2723a5bf9a18743

18,682

md

Markdown

CHANGELOG.md

bjkastel/gitlab-oauth-plugin

44240406f68884c356e810b1e1252503446afd3a

[ "MIT" ]

27

2016-07-12T08:33:47.000Z

2022-03-30T08:39:40.000Z

CHANGELOG.md

bjkastel/gitlab-oauth-plugin

44240406f68884c356e810b1e1252503446afd3a

[ "MIT" ]

25

2016-08-22T08:55:05.000Z

2022-03-31T21:59:17.000Z

CHANGELOG.md

bjkastel/gitlab-oauth-plugin

44240406f68884c356e810b1e1252503446afd3a

[ "MIT" ]

47

2016-07-06T20:08:25.000Z

2022-03-13T18:04:38.000Z

1.10 ----------------------------------------------------------------------------------- - **Dominic** : Fix org comparison bug (#28) - **Dominic** : Use group path from API (#29) - **Mohamed EL Habib** : add 1.9 changes 1.9 ----------------------------------------------------------------------------------- - **Wadeck Follonier** : [JEP-227] Prevent Stackoverflow during logout (#27) 1.8 ----------------------------------------------------------------------------------- - **kwening** : added hudson.model.Item.Discover permission to read permission checks (#25) 1.7 ----------------------------------------------------------------------------------- - **Dmitry Erastov** : Include scope in `/oauth/authorize` URL (#26) 1.6 ----------------------------------------------------------------------------------- - **Odilo Oehmichen** : introduces gitlab groups for admins (#23) - **Demenev Anton** : Fix group and organisation check. (#21) - **Flemming Frandsen** : Fixed the horrendous security problem caused by not qualifying groups with the parent groups and making sure that groups cannot be conflated with users (#22) - **Oleg Nenashev** : Reorder content on the README page to be more user-focused (#20) - **Zbynek Konecny** : Badges link to plugin site - **Zbynek Konecny** : Use GitHub as source of documentation - **Zbynek Konecny** : Clean up markdown - **Zbynek Konecny** : Update documentation links - **Zbynek Konecny** : Import Wiki documentation - **Mohamed EL Habib** : fixed build status and link 1.5 ----------------------------------------------------------------------------------- - **Giulio Ruggeri** : Changed redirect url build using jenkins root url (#15) - **Bjoern Kasteleiner** : JENKINS-59069 / SECURITY-795: Fix session fixation vulnerability (#16) - **Wadeck Follonier** : [SECURITY-796][JENKINS-59069](https://issues.jenkins.io/browse/JENKINS-59069) Open redirect prevention (#17) - **johny.zheng** : Grant STOP Build permissions to all Authenticated Users (#14) - **isaacdong** : [JENKINS-52129](https://issues.jenkins.io/browse/JENKINS-52129) 1. bug fixed: repository.isPublic returns null. 2 add 2 git URL patterns without "git@". 1.4 ----------------------------------------------------------------------------------- - **Mario Steinitz** : [JENKINS-50838](https://issues.jenkins.io/browse/JENKINS-50838) Change GitLab API support from v3 to v4. 1.3 ----------------------------------------------------------------------------------- - **Mohamed EL Habib** : [JENKINS-47097](https://issues.jenkins.io/browse/JENKINS-47097) added support to login using gitlab private token 1.2 ----------------------------------------------------------------------------------- - **Mohamed EL Habib** : [JENKINS-44489](https://issues.jenkins.io/browse/JENKINS-44489) fixed findbug introduced by 987608a commit - **Mohamed EL Habib** : [JENKINS-44489](https://issues.jenkins.io/browse/JENKINS-44489) fixed logout when the plugin is configured to allow READ permission for Authenticated, but not Anonymous users. - **Mohamed EL Habib** : add jenkins file to build into ci.jenkins.io 1.1 ----------------------------------------------------------------------------------- - **Mohamed EL Habib** : remove redundant NULL check - **Mohamed EL Habib** : upgrade jenkins parent and dependencies versions - **Wadeck Follonier** : - with import it's better - **Wadeck Follonier** : FireAuthenticed no more required reflection - as the core dependency is now set to 1.625.3 - **Artur Malinowski** : Fixed IndexOutOfBoundsException when user has no group 1.0.9 ----------------------------------------------------------------------------------- - **Jairo Ricarte** : [JENKINS-37741](https://issues.jenkins.io/browse/JENKINS-37741) Testing /project path ont allowGitlabWebHookPermission check - **Jairo Ricarte** : added new path for gitlab-plugin's webhook using anonymous permission 1.0.8 ----------------------------------------------------------------------------------- - **wzxjohn** : Finish permission by gitlab feature 1.0.7 ----------------------------------------------------------------------------------- - **wzxjohn** : [JENKINS-37517](https://issues.jenkins.io/browse/JENKINS-37517) Fix login fails because of a GitLab Api Bug Use v1.2.6 of GitLab Api Client to fix this issue. - **wzxjohn** : [JENKINS-37518](https://issues.jenkins.io/browse/JENKINS-37518) Fix api url problem New GitLab Api Client will automatically add api/v3 so we do not need to add api/v3 in config. Maybe this config node can be delete in the future. - **wzxjohn** : Fix ERROR: Failed to load help file: Not Found when click the '?' beside "Grant READ permissions for /gitlab-webhook" - **wzxjohn** : [JENKINS-37049](https://issues.jenkins.io/browse/JENKINS-37049) License issue 1.0.6 ----------------------------------------------------------------------------------- 1.0.5 ----------------------------------------------------------------------------------- - **Thorsten** : Change HttpClient configuration to drop usage of methods flagged as @deprecated - **Jairo Ricarte** : [JENKINS-36075](https://issues.jenkins.io/browse/JENKINS-36075)GitLab oauth does not display in Security Realm 1.0.4 ----------------------------------------------------------------------------------- - **Mohamed EL HABIB** : remove oauthScopes - **Mohamed EL HABIB** : upgrade pom parent 1.0.3 ----------------------------------------------------------------------------------- 1.0.3 ----------------------------------------------------------------------------------- 1.0.2 ----------------------------------------------------------------------------------- 1.0.1 ----------------------------------------------------------------------------------- - **Mohamed EL HABIB** : update pom version 1.0.0 ----------------------------------------------------------------------------------- - **Mohamed EL HABIB** : fixed jira add github link - **Mohamed EL HABIB** : remove unused code - **Mohamed EL HABIB** : fixed licence copyright - **Mohamed EL HABIB** : cleanup code style - **Mohamed EL HABIB** : using 1.113 version of the hpi-plugin, starting from 1.114 gitlab real is not actif into security section - **Mohamed EL HABIB** : fixed non serializable field in serializable class - **Mohamed EL HABIB** : fixed findbug : potential NPE - **Mohamed EL HABIB** : fixed missing hashCode when equals is implemented - **Mohamed EL HABIB** : fixed unit test after mvn parent upgrade - **Mohamed EL HABIB** : upgrade mvn parent pom and clean pom - **Mohamed EL HABIB** : fixed jelly config file path case - **Mohamed EL HABIB** : fixed migration from github to gitlab - **Mohamed EL HABIB** : remove scope (not supported by gitlab) + fix gitlabWebUri not shown into configuration ui - **Mohamed EL HABIB** : replace github by gitlab - **Mohamed EL HABIB** : alpha version extracted from github-oauth-plugin - **Mohamed EL HABIB** : alpha version extracted from github-oauth-plugin - **Seth Rosenblum** : Reduce read access log messages to finest - **Sam Gleske** : Revert "Update wiki page URL. Disappeared from the update" - **Sam Gleske** : Update wiki page URL. Disappeared from the update - **Sam Gleske** : Private memberships can be used for authorization - **Sam Gleske** : Allow limited oauth scopes - **Sam Gleske** : Allow Jenkins email to be set using private email - **Sam Gleske** : Automation equals methods - **Sam Gleske** : Fix Java 7 compatibility when running unit tests. - **Sam Gleske** : Fix migrating settings from plugin 0.20 to 0.21+ - **Sam Gleske** : Fix wiki link in README. - **Sam Gleske** : New README and CONTRIBUTING document - **Joshua Hoblitt** : fix whitespace - **Pascal Widdershoven** : Add support for allowing anonymous ViewStatus permission - **Julien Carsique** : JENKINS-21331: include teams as groups - **Stephen Rosen** : Fix default oauth scope in jelly conf - **Stephen Rosen** : Restrict default OAuthScope to "read:org" - **Sam Gleske** : Update current maintainers in pom.xml - **Michael Neale** : allow github oauth tokens to be used to access jenkins api - **Joshua Hoblitt** : make Github OAuth Scopes configurable - **Alex Rothenberg** : Fix for when user enters a badly formed github url for repo - **Surya Gaddipati** : Update to newer version of github api - **Jesse Glick** : Adding TODO comment to match e1e10c896dbcf0636222f52e2308d0ebcfe778ef. - **Alex Rothenberg** : updated isPublicRepository check to cache results - **Matt Aken** : Use asList() to eagerly walk all repositories - **Alex Rothenberg** : Optimize the number of github api calls for authorization checks - **Kohsuke Kawaguchi** : Use Jenkins' proxy configuration - **Kohsuke Kawaguchi** : Unneeeded check as githubWebUri is guaranteed non-null at this point. - **Kohsuke Kawaguchi** : Restoring backward compatible constructor - **Kohsuke Kawaguchi** : Call fireAuthenticated if we can. - **Surya Gaddipati** : Revert "Fire SecurityListener#authenticated after user is authenticated." - **Surya Gaddipati** : Upgrade github-api to 1.54 - **Surya Gaddipati** : Upgrade github-api version dependency to 1.53 - **Kohsuke Kawaguchi** : [FIXED JENKINS-23254] - **Sam Kottler** : Bump the maven-hpi-plugin version - **Soren Hansen** : Make no assumption about user's existence - **Sam Kottler** : Start fixing indentation issues - **Jon San Miguel** : Add read:org scope to see private organization memberships - **Alex Rothenberg** : A flag to allow authenticated users to create new jobs - **Alex Rothenberg** : added an "isUseRepositoryPermissions" so the admin checkbox in jelly works - **Marton Sereg** : fixed formatting - **Marton Sereg** : Fixed issue with Jenkins CLI public key authentication - **Alex Rothenberg** : fixed bug with empty git repository url causing NullPointerException - **Alex Rothenberg** : removed some unnecessary lines in tests - **Alex Rothenberg** : removed innacurate copyright notice - **Alex Rothenberg** : User controllable flag to enable/disable reposistory authorization - **Alex Rothenberg** : Repository based authorization - **Sam Kottler** : Add myself as copyright holder for 2013-2014 - **Soren Hansen** : With no auth token, we are not sure if users exist - **Surya Gaddipati** : Use hasExplicitlyConfiguredAddress instead of getAddress(which scans all projects and builds to find users's email address) - **Tamás Földesi** : Add support for proxy - **Surya Gaddipati** : Dont attempt to set email address property for a user upon login - **Sam Kottler** : Add skottler to the developer list - **Kohsuke Kawaguchi** : Missing dependency in POM - **Oren Held** : Do not overwrite user's email, unless it's empty (cherry picked from commit 88f6ee7c893bf509527df6c965e495c0d145c60c) - **Kohsuke Kawaguchi** : simplifying the caching code by using Guava - **OHTAKE Tomohiro** : Expose getGithubApiUri to jelly - **Tomas Varaneckas** : Adding missing TimeUnit import - **Tomas Varaneckas** : Improving organization cache timeout readability - **Aaron Crickenberger** : Depend on latest LTS plugin version - **Aaron Crickenberger** : Avoid NPE for anonymous admin permissions check - **Johno Crawford** : Optimise imports. - **Bo Jeanes** : Add an explicit API URI field to GithubSecurityRealm - **Bo Jeanes** : Bump github-api dependency to 1.40 - **Tomas Varaneckas** : Resetting organization cache timer - **Luís Faceira** : Close #18 - Basic API authentication is possible again - **Tomas Varaneckas** : Github organization cache for much faster jenkins UI navigation for non admin users - **Johno Crawford** : Revert "Do not strip protocol from end point." - **johnou** : Do not strip protocol from end point. - **brettlangdon** : changed all occurrences of github.com/account/applications/new to github.com/settings/applications/new - **Kohsuke Kawaguchi** : Using the latest to fix V2 API removal - **Kohsuke Kawaguchi** : Updated to v1.27 to remove the V2 API dependency - **Kohsuke Kawaguchi** : exposing OAuth access token programmatically. - **Kohsuke Kawaguchi** : when the user logs in, transcribe his name and e-mail address - **Michael O'Cleirigh** : bump up the development version to 0.12-SNAPSHOT - **Alistair Jones** : Target exact URIs instead of using regular expressions. - **Alistair Jones** : Punch a security hole for cc.xml - **Alistair Jones** : Ignore IntelliJ files - **Alistair Jones** : Quick fix for compilation error - **Alistair Jones** : Use repositories suggested in plugin tutorial: https://wiki.jenkins-ci.org/display/JENKINS/Plugin+tutorial - **Michael O'Cleirigh** : bump up development version to 0.11-SNAPSHOT - **Michael O'Cleirigh** : Update github-api-plugin version to 1.17 - **Michael O'Cleirigh** : Fix #16 to support API calls against github enterprise installations. - **Michael O'Cleirigh** : update next plugin version to 0.10-SNAPSHOT - **Michael O'Cleirigh** : Add in m2e exclusion for maven-hpi-plugin - **Kohsuke Kawaguchi** : depend on the github-api plugin so pick up github-api jar - **Kohsuke Kawaguchi** : added a mechanism for other plugins to request additional scopes - **Kohsuke Kawaguchi** : After the authentication, send the user back to where he came from - **Kohsuke Kawaguchi** : expose the authenticated GitHub object to enable further operations - **Kohsuke Kawaguchi** : Use organizations as groups - **Michael O'Cleirigh** : Implement user lookup by name for JENKINS-11246 - **Michael O'Cleirigh** : JENKINS-11246 item one: authenticated READ with unlimited access - **Michael O'Cleirigh** : Add ignore entries for eclipse indigo compatilibity - **Michael O'Cleirigh** : bump up the development version to 0.9-SNAPSHOT - **Michael O'Cleirigh** : Fix typo in Converter - **Michael O'Cleirigh** : Add Converter implementation to GithubSecurityRealm - **Michael O'Cleirigh** : Fix upgrade issue in 0.7 - **Michael O'Cleirigh** : bump up development verion to 0.8-SNAPSHOT - **Michael O'Cleirigh** : Add help to the Security Realm section. - **Dave Dopson** : adding support for changing the github uri (eg for Github Enterprise Edition) - **Michael O'Cleirigh** : bump up the development version to 0.7-SNAPSHOT - **Michael O'Cleirigh** : Add delegate method to ACL to show Anonymous READ permission. - **Michael O'Cleirigh** : Implement issue #2 toggle for anonymous READ's - **Michael O'Cleirigh** : bump up the development version to 0.6-SNAPSHOT - **Michael O'Cleirigh** : Now only log on successful acceptance of the github-webhook url - **Michael O'Cleirigh** : Modify logger settings to be less verbose. - **Michael O'Cleirigh** : Add logger statements when access is granted - **Michael O'Cleirigh** : Add additional full url tests and the tested regex into the ACL - **Michael O'Cleirigh** : Add testcase for issue #6 and issue #1 - **Michael O'Cleirigh** : Add licence header to all of the source files - **Michael O'Cleirigh** : bump up current development version to 0.5-SNAPSHOT - **Vladimir Kravets** : github-webhook detection fix again - **Michael O'Cleirigh** : broaden the github-webhook url test - **Michael O'Cleirigh** : bump plugin version to 0.4-SNAPSHOT - **Vladimir Kravets** : Fix to check request URI for github-webhook if it's located in non ROOT folder. E.g. http://jenkins.com/jenkins/github-webhook - **Michael O'Cleirigh** : Add compatibility flag since the on disk format has changed. - **Michael O'Cleirigh** : Beutify how the admin users and authorized organizations are displayed. - **Michael O'Cleirigh** : Split out ACL from Authorization Strategy. - **Michael O'Cleirigh** : Set build encoding to UTF-8 - **Michael O'Cleirigh** : Update Readme.md for the new webhook permission. - **Michael O'Cleirigh** : Remove build token support in favor of github-plugin webhook. - **Michael O'Cleirigh** : extract the project name from the request to lookup the build token. - **Michael O'Cleirigh** : allow read access to /job/.*/build urls - **Michael O'Cleirigh** : add in note about having to be a public member in the organization - **Michael O'Cleirigh** : bump up development version to 0.3-SNAPSHOT - **Michael O'Cleirigh** : Fix AuthorizationStrategy serialization bug - **Michael O'Cleirigh** : allow anonymous read. - **Michael O'Cleirigh** : change security components to require GithubAuthenticationToken - **Michael O'Cleirigh** : bump up plugin version to 0.2-SNAPSHOT - **Michael O'Cleirigh** : Change Artifactid to github-oauth to make help work. - **Michael O'Cleirigh** : @Ignore the testcase as it needs oauth credentials to work. - **Michael O'Cleirigh** : change snapshot version to 0.1-SNAPSHOT - **Michael O'Cleirigh** : moved help into the webapp directory - **Michael O'Cleirigh** : Fix display of authorization strategy properties - **Michael O'Cleirigh** : move to markdown enabled README - **Michael O'Cleirigh** : Define <scm>, <url> and bump github-api to 1.10 - **Michael O'Cleirigh** : add in example application entry including callback url. - **Michael O'Cleirigh** : update README and remove git dependency - **Michael O'Cleirigh** : Add in test case with api details externalized through Systetm Properties - **Michael O'Cleirigh** : merged both ACL's into one and it is now the root ACL. - **Michael O'Cleirigh** : Use new command from github-api to get list of organizations of a user. - **Michael O'Cleirigh** : Switch to using the github-api artifact - **Michael O'Cleirigh** : implement github authorization strategy - **Michael O'Cleirigh** : update pom to 1.419 parent and remove unneeded dependencies. - **Michael O'Cleirigh** : Fix formatting of GithubAuthenticationToken class - **Michael O'Cleirigh** : authentication works but authorization needs work - **Michael O'Cleirigh** : Remote API calls using the token work. - **Michael O'Cleirigh** : remove federatedloginservice subclass to focus only on security realm. - **Michael O'Cleirigh** : Login link starts the authentication process. - **Michael O'Cleirigh** : add in readme file - **Michael O'Cleirigh** : credit the mysql-auth-plugin in the GithubSecurityRealm class - **Michael O'Cleirigh** : jelly works and security realm is selectable in jenkins. - **Michael O'Cleirigh** : pull in configsettings from the mysql-auth-plugin and the twitter-jenkins-plugins - **Michael O'Cleirigh** : testing out various jenkins parts - **Michael O'Cleirigh** : include generated eclipse files in .gitignore - **Michael O'Cleirigh** : insert licence and developers section into pom - **Michael O'Cleirigh** : initial commit

66.721429

247

0.662777

eng_Latn

0.821762

e9784cb4cd1dd19239eb27e29f2bc24c6f19b76f

4,049

md

Markdown

docs/es/sql-reference/table-functions/remote.md

evryfs/ClickHouse

a9648af0b9e2506ce783106315814ed8dbd0a952

[ "Apache-2.0" ]

18

2021-05-29T01:12:33.000Z

2021-11-18T12:34:48.000Z

docs/es/sql-reference/table-functions/remote.md

evryfs/ClickHouse

a9648af0b9e2506ce783106315814ed8dbd0a952

[ "Apache-2.0" ]

13

2019-06-06T09:45:53.000Z

2020-05-15T12:03:45.000Z

docs/es/sql-reference/table-functions/remote.md

evryfs/ClickHouse

a9648af0b9e2506ce783106315814ed8dbd0a952

[ "Apache-2.0" ]

22

2019-06-14T10:31:51.000Z

2020-10-12T14:57:44.000Z

--- machine_translated: true machine_translated_rev: 72537a2d527c63c07aa5d2361a8829f3895cf2bd toc_priority: 40 toc_title: remoto --- # remoto, remoteSecure {#remote-remotesecure} Le permite acceder a servidores remotos sin crear un `Distributed` tabla. Firma: ``` sql remote('addresses_expr', db, table[, 'user'[, 'password']]) remote('addresses_expr', db.table[, 'user'[, 'password']]) remoteSecure('addresses_expr', db, table[, 'user'[, 'password']]) remoteSecure('addresses_expr', db.table[, 'user'[, 'password']]) ``` `addresses_expr` – An expression that generates addresses of remote servers. This may be just one server address. The server address is `host:port` o simplemente `host`. El host se puede especificar como nombre de servidor o como dirección IPv4 o IPv6. Una dirección IPv6 se especifica entre corchetes. El puerto es el puerto TCP del servidor remoto. Si se omite el puerto, utiliza `tcp_port` del archivo de configuración del servidor (por defecto, 9000). !!! important "Importante" El puerto es necesario para una dirección IPv6. Ejemplos: ``` text example01-01-1 example01-01-1:9000 localhost 127.0.0.1 [::]:9000 [2a02:6b8:0:1111::11]:9000 ``` Se pueden separar varias direcciones por comas. En este caso, ClickHouse usará procesamiento distribuido, por lo que enviará la consulta a todas las direcciones especificadas (como a fragmentos con datos diferentes). Ejemplo: ``` text example01-01-1,example01-02-1 ``` Parte de la expresión se puede especificar entre llaves. El ejemplo anterior se puede escribir de la siguiente manera: ``` text example01-0{1,2}-1 ``` Los corchetes rizados pueden contener un rango de números separados por dos puntos (enteros no negativos). En este caso, el rango se expande a un conjunto de valores que generan direcciones de fragmentos. Si el primer número comienza con cero, los valores se forman con la misma alineación cero. El ejemplo anterior se puede escribir de la siguiente manera: ``` text example01-{01..02}-1 ``` Si tiene varios pares de llaves, genera el producto directo de los conjuntos correspondientes. Las direcciones y partes de las direcciones entre llaves se pueden separar mediante el símbolo de tubería (\|). En este caso, los conjuntos de direcciones correspondientes se interpretan como réplicas y la consulta se enviará a la primera réplica en buen estado. Sin embargo, las réplicas se iteran en el orden establecido actualmente en el [load_balancing](../../operations/settings/settings.md) configuración. Ejemplo: ``` text example01-{01..02}-{1|2} ``` En este ejemplo se especifican dos fragmentos que tienen dos réplicas cada uno. El número de direcciones generadas está limitado por una constante. En este momento esto es 1000 direcciones. Uso de la `remote` función de la tabla es menos óptima que la creación de un `Distributed` mesa, porque en este caso, la conexión del servidor se restablece para cada solicitud. Además, si se establecen nombres de host, los nombres se resuelven y los errores no se cuentan cuando se trabaja con varias réplicas. Cuando procese un gran número de consultas, cree siempre el `Distributed` mesa antes de tiempo, y no utilice el `remote` función de la tabla. El `remote` puede ser útil en los siguientes casos: - Acceder a un servidor específico para la comparación de datos, la depuración y las pruebas. - Consultas entre varios clústeres de ClickHouse con fines de investigación. - Solicitudes distribuidas poco frecuentes que se realizan manualmente. - Solicitudes distribuidas donde el conjunto de servidores se redefine cada vez. Si el usuario no está especificado, `default` se utiliza. Si no se especifica la contraseña, se utiliza una contraseña vacía. `remoteSecure` - igual que `remote` but with secured connection. Default port — [Tcp_port_secure](../../operations/server-configuration-parameters/settings.md#server_configuration_parameters-tcp_port_secure) de config o 9440. [Artículo Original](https://clickhouse.tech/docs/en/query_language/table_functions/remote/)

47.081395

455

0.777229

spa_Latn

0.989631

e97947da6be82cc659db64086d0a9f3db7973d02

2,791

md

Markdown

README.md

whitewalker-sa/todo

9c6a4a474339abf3589530ec7d0b20ec6fd68b8f

[ "MIT" ]

null

README.md

whitewalker-sa/todo

9c6a4a474339abf3589530ec7d0b20ec6fd68b8f

[ "MIT" ]

null

README.md

whitewalker-sa/todo

9c6a4a474339abf3589530ec7d0b20ec6fd68b8f

[ "MIT" ]

null

## Usage ![alt text](https://i.ibb.co/xJLFY9P/todo.png) ```bash Select the api row you want to call Collapse the row on the far right with the drop down icon Click the the button "Try it Now" Modify your parameters by id(primary key), firstName, lastName or todo title. Press the button Execute If status code '200' or '201' is returned, the call was successful. ``` ## Description NodeJS application that manages a database of users and a todo list for each user . The application uses NestJS Framework RESTful API, MySQL and Swagger documentation ## Installation ```bash $ git clone https://github.com/whitewalker-sa/todo.git $ cd todo $ npm install ``` ## Running the app ```bash # development $ npm run start # watch mode $ npm run start:dev # production mode $ npm run start:prod Navigate to 'http://localhost:3000/#/users' or 'http://localhost:3000/#/todos' to make CRUD API call using SWAGGER API UI. Alternatively you may use Postman for API testing ``` Next up, generate mysql database. If you already have mysql in your development environment, you can use that. But if you don't have mysql database, try this process. Install docker for your OS and run following commands. If your docker is successfully installed, you can use docker cli. ```bash docker run --name nest -d -p 3306:3306 -e MYSQL_DATABASE=test -e MYSQL_ROOT_PASSWORD=root -v ~/database/nest:/var/lib/mysql mysql:5.7 ``` And then, you can connect mysql in http://localhost:3306, username 'root' and password is 'root'. ## Start with docker Build the image using docker cli ```bash docker build -t user-todo-api . docker images # list up docker images ``` And then you can create and run docker container using builded image. ```bash docker run -d -p 3000:3000 user-todo-api docker ps # list up running container ``` ## Test ```bash # unit tests $ npm run test # e2e tests $ npm run test:e2e # test coverage $ npm run test:cov ``` ## Start with docker compose Docker compose in this project is include api and mysql 5.7 for database. Run followed command in project directory. ```bash docker-compose up -d # build images, create and run containers in background ``` If container is created, you can access api on http://localhost:3000/#/. And you can access database through http://localhost:3306. ## Access phpmyadmin to view API call changes in MySQL database ```bash Ensure that mysql server is running on port 3036 Type 'http://localhost/phpmyadmin' in the browser Login 'root' password 'root' database_name 'test' ``` ## Stay in touch - Author - [Mpho Louis](https://kamilmysliwiec.com) - Twitter - [@whitewalker_01](https://twitter.com/whitewalker_01) - Linkedin [Linkedin](https://linkedin.com/in/mpho-louis) ## License [MIT licensed](LICENSE).

21.804688

166

0.731279

eng_Latn

0.917004

e9794ebeadd7dae91cee065f0731529743936db8

4,539

md

Markdown

README.md

ZBT-Tools/PEMFC-Model

9dcd4d78f316bd6a5e3a777c7c01756a428d16ca

[ "MIT" ]

4

2021-10-21T13:22:14.000Z

2022-03-16T11:52:40.000Z

README.md

ZBT-Tools/PEMFC-Model

9dcd4d78f316bd6a5e3a777c7c01756a428d16ca

[ "MIT" ]

27

2018-11-30T17:08:51.000Z

2022-01-20T15:24:08.000Z

README.md

ZBT-Tools/PEMFC-Model

9dcd4d78f316bd6a5e3a777c7c01756a428d16ca

[ "MIT" ]

7

2019-03-11T03:34:56.000Z

2022-03-19T03:58:13.000Z

# PEMFC-Stack-Model A reduced dimensional numerical model to simulate the performance of PEM fuel cell stacks developed in Python 3.6 utilizing the numerical libraries NumPy and SciPy. #### Geometric Layout ![alt text](./data/stack_layout.png "Stack Layout") #### Features - Physical stack domain is discretized into two dimensions: - through each cell in the direction of the electrical current (current-direction) - along the flow direction of each channel (flow-direction) - Calculation of the reactant flow distribution into the cells based on the geometry of headers and channels - Local current distribution along the flow- and current-direction due to: - reactant transport within the channels and the porous media - temperature distribution - reaction kinetics and voltage losses according to Kulikovsky (2013) - Temperature distribution along the flow- and current-direction with a discretization in the current-direction (through plane) in five nodes at the interfaces of: - anodic and cathodic bipolar plates (BPP-BPP) - anodic bipolar plate and gas diffusion electrode (BPP-GDE, Ano) - anodic gas diffusion electrode and membrane (GDE-Mem, Ano) - cathodic gas diffusion electrode and membrane (GDE-Mem, Cat) - cathodic bipolar plate and gas diffusion electrode (BPP-GDE, Cat) # Minimum requirements - NumPy 1.14.3 - SciPy 1.1.0 - Matplotlib 2.2.2 # Usage Download the repository, review settings in the pemfc/settings folder (ouput.py, geometry.py, operating_conditons.py, physical_properties.py, simulation.py). Then execute ```python python -m pemfc.main_app ``` for the CLI app, or ```python python -m pemfc.gui_app ``` for the GUI app from the repository folder with your Python interpreter. Input parameters can be adjusted via GUI (work in progress) or in the corresponding files in the pemfc/settings folder. If not specified otherwise, a folder called "output" will be created at the end of a simulation run, which contains the results in various data files and plots. # Implementation ![alt text](./data/class_structure.svg "Class Structure") # References #### Stack discretization, temperature coupling, reactant transport according to: *Chang, Paul, Gwang-Soo Kim, Keith Promislow, and Brian Wetton. “Reduced Dimensional Computational Models of Polymer Electrolyte Membrane Fuel Cell Stacks.” Journal of Computational Physics 223, no. 2 (May 2007): 797–821. https://doi.org/10.1016/j.jcp.2006.10.011.* #### Membrane models as described in: *Springer, T. E., T. A. Zawodzinski, and S. Gottesfeld. “Polymer Electrolyte FuelCell Model.” Journal of The Electrochemical Society 138, no. 8 (August 1, 1991): 2334–42. https://doi.org/10.1149/1.2085971.* *Kamarajugadda, Sai, and Sandip Mazumder. “On the Implementation of Membrane Models in Computational Fluid Dynamics Calculations of Polymer Electrolyte Membrane Fuel Cells.” Computers & Chemical Engineering 32, no. 7 (July 2008): 1650–60. https://doi.org/10.1016/j.compchemeng.2007.08.004.* *Nguyen, Trung V., and Ralph E. White. “A Water and Heat Management Model for Proton‐Exchange‐Membrane Fuel Cells.” Journal of The Electrochemical Society 140, no. 8 (August 1, 1993): 2178–86. https://doi.org/10.1149/1.2220792.* *Xu, Feina, Sébastien Leclerc, Didier Stemmelen, Jean-Christophe Perrin, Alain Retournard, and Daniel Canet. “Study of Electro-Osmotic Drag Coefficients in Nafion Membrane in Acid, Sodium and Potassium Forms by Electrophoresis NMR.” Journal of Membrane Science 536 (August 2017): 116–22. https://doi.org/10.1016/j.memsci.2017.04.067.* *Peng, Zhe, Arnaud Morin, Patrice Huguet, Pascal Schott, and Joël Pauchet. “In-Situ Measurement of Electroosmotic Drag Coefficient in Nafion Membrane for the PEMFC.” The Journal of Physical Chemistry B 115, no. 44 (November 10, 2011): 12835–44. https://doi.org/10.1021/jp205291f.* #### Manifold model and flow distribution based on: *Koh, Joon-Ho, Hai-Kyung Seo, Choong Gon Lee, Young-Sung Yoo, and Hee Chun Lim. “Pressure and Flow Distribution in Internal Gas Manifolds of a Fuel-Cell Stack.” Journal of Power Sources 115, no. 1 (March 2003): 54–65. https://doi. org/10.1016/S0378-7753(02)00615-8.* #### Electrochemical reaction kinetics and transport losses according to: *Kulikovsky, A. A. “A Physically–Based Analytical Polarization Curve of a PEM Fuel Cell.” Journal of the Electrochemical Society 161, no. 3 (December 28, 2013): F263–70. https://doi.org/10.1149/2.028403jes.*

42.027778

83

0.753029

eng_Latn

0.854956

e979ec21cc8f60db8ac6edae4758a59770c4090f

420

md

Markdown

README.md

MohammedAlagha/mypos

abbec08c6fe5268d972a02212867ffb65d30b3ce

[ "MIT" ]

null

README.md

MohammedAlagha/mypos

abbec08c6fe5268d972a02212867ffb65d30b3ce

[ "MIT" ]

4

2021-03-10T01:09:36.000Z

2022-02-18T16:29:42.000Z

README.md

MohammedAlagha/mypos

abbec08c6fe5268d972a02212867ffb65d30b3ce

[ "MIT" ]

null

## About my pos Open source mypos Laravel 6 . ## Version laravel 5.7 - Bootstrap 4 ### How to Install - copy files in your local directory - rename env.example to .env file and set your db connection data - run composer install - run php artisan key:generate - run command "php artisan migrate --seed" ### Server Requirements - PHP >= 7.2.0 License ======= Code released under the MIT license

13.548387

66

0.678571

eng_Latn

0.972461

e97a14a9df8e4e964b91cb10c96a96819c2e7041

8,769

md

Markdown

src/content/guidelines/motion/basics.md

kellychurchill/website

d8442229bec305e984d2c9cd37e2273cd6cabcba

[ "Apache-2.0" ]

6

2019-02-19T16:44:25.000Z

2019-04-09T12:45:40.000Z

src/content/guidelines/motion/basics.md

kellychurchill/website

d8442229bec305e984d2c9cd37e2273cd6cabcba

[ "Apache-2.0" ]

28

2019-02-04T20:11:37.000Z

2019-04-03T15:48:02.000Z

src/content/guidelines/motion/basics.md

ibm-frontend/carbon-website

fcb286afbe5fce0b93223a762c42babe01ee2642

[ "Apache-2.0" ]

7

2019-02-04T22:39:38.000Z

2019-03-06T23:26:16.000Z

--- label: Motion can bring your work to life, guide users through complex experiences, and help move forward—from here to there, now to next, start to finish—and make progress. title: Motion tabs: ['Basics', 'Choreography', 'Resources'] --- ## Resources <grid-wrapper col_lg="8" flex="true" bleed="true"> <clickable-tile title="Motion Generator" href="https://ibm.github.io/motion/" type="resource"></clickable-tile> <clickable-tile title="IBM Motion Package" href="https://github.com/IBM/carbon-elements/tree/master/packages/motion" type="resource"></clickable-tile> </grid-wrapper> <anchor-links> <ul> <li><a data-scroll href="#style">Style</a></li> <li><a data-scroll href="#easing">Easing</a></li> <li><a data-scroll href="#duration">Duration</a></li> </ul> </anchor-links> ## Style IBM Design System recognizes different moments in user's experience, and offers two styles of motion - the Productive motion, and the Expressive motion. The motion curves are designed to reflect the philosophical duality of Man and Machine. <website-tabs> <tab label="Curves"><div> <simple-columns gutter=true> <div> <p>Productive</p> <img src="images/Motion_overview_Curves_productive.svg" alt="Curve graphs representing differences between Productive and Expressive animation curves" /> </div> <div> <p>Expressive</p> <img src="images/Motion_overview_Curves_expressive.svg" alt="Curve graphs representing differences between Productive and Expressive animation curves" /> </div> </simple-columns> </div></tab> <tab label="Abstract"> <div> `vimeo: https://vimeo.com/310583009` </div></tab> <tab label="In-situ"><div> `vimeo: https://vimeo.com/310583036` </div></tab> </website-tabs> ### Productive Productive motion create a sense of efficiency and responsiveness, while being subtle. Use productive motion for moments when user needs to focus on tasks — micro-interactions such as button interaction and dropdown menus, revealing additional information upon user's request, or rendering data tables and visualizations. ### Expressive Expressive motion delivers enthusiastic and vibrant, thus more visible movement. Use expressive motion for significant moments such as user opening a new page or clicking the primary action button, or when the movement itself conveys a meaning or needs to be noticed by the user such as system alert or notification box appearing. Productive and Expression are both essential to an interface. Reserve Expressive motion for occasional, important moments to better capture user’s attention, and offer rhythmic break to the productive experience. Our [Components](../../components/overview/) have basic motion build in. Use this guidance to customize motion, combine and coordinate motion through out experiences. <grid-wrapper col_lg="12" flex="true"> <do-dont-example correct="true" full_width="true" label="Productive moments are labeled blue, and expressive moments are labeled magenta."> `vimeo: https://vimeo.com/310583077` </do-dont-example> </grid-wrapper> ## Easing Strictly linear movement appears unnatural to the human eye. Elements on the screen speed up quickly and slow down smoothly, obeying the physics of a light-weight material. "Easing curves" describe the precise amount of accelerations in motion. We commonly use one of these three types of easing. <grid-wrapper col_lg="8" flex="true"> <do-dont-example correct="true" full_width="true" label="Elements on the screen speed up quickly and slow down smoothly, obeying the physics of a light-weight material."> `vimeo: https://vimeo.com/310582370` </do-dont-example> </grid-wrapper> Avoid easing curves that are unnatural, distracting, or decorative should be avoided. IBM motion is essential and efficient. We guide the users to value as quickly as possible. <grid-wrapper col_lg="8" flex="true"> <do-dont-example correct="false" full_width="true" label="Easing curves that suggest bounce, stretch, or sudden stops are not recommended."> `vimeo: https://vimeo.com/310582418` </do-dont-example> </grid-wrapper> ### Standard easing Use `standard-easing` when an element is visible from the beginning to end of a motion. Tiles expanding and table rows sorting are good examples. <website-tabs> <tab label="Curves"> <div> `vimeo: https://vimeo.com/310582611` </div> </tab> <tab label="Examples"> <div> `vimeo: https://vimeo.com/310582667` </div> </tab> </website-tabs> | Curves | Productive | Expressive | |---------------|---------------------------------|---------------------------------| | CSS | cubic-bezier(0.2, 0, 0.38, 0.9) | cubic-bezier(0.4, 0.14, 0.3, 1) | | After Effects | Outgoing 20%, incoming 62% | Outgoing 40%, incoming 70% | ### Entrance easing Use `entrance-ease` when adding elements to the view such as a modal or toaster appearing, or moving in response to users' input, such as dropdown opening or toggle. An element quickly appears and slows down to a stop. <website-tabs> <tab label="Curves"> <div> `vimeo: https://vimeo.com/310582467` </div> </tab> <tab label="Examples"> <div> `vimeo: https://vimeo.com/310582503` </div> </tab> </website-tabs> | Curves | Productive | Expressive | |---------------|---------------------------------|---------------------------------| | CSS | cubic-bezier(0, 0, 0.38, 0.9) | cubic-bezier(0, 0, 0.3, 1) | | After Effects | Outgoing 0%, incoming 62% | Outgoing 0%, incoming 70% | ### Exit easing Use `exit-easing` when removing elements from view, such as closing a modal or toaster. The element speeds up as it exits from view, implying that its departure from the screen is permanent. <website-tabs> <tab label="Curves"> <div> `vimeo: https://vimeo.com/310582530` </div> </tab> <tab label="Examples"> <div> `vimeo: https://vimeo.com/310582574` </div> </tab> </website-tabs> | Curves | Productive | Expressive | |---------------|---------------------------------|---------------------------------| | CSS | cubic-bezier(0.2, 0, 1, 0.9) | cubic-bezier(0.4, 0.14, 1, 1) | | After Effects | Outgoing 20%, incoming 0% | Outgoing 40%, incoming 0% | An exception to exits: if an element leaves the view but stays nearby, ready to reappear upon user action, use Standard easing instead. A good example of this is a side panel. The panel would leave the view, but slows down as it exits, implying that it would come to rest just outside the view, and ready to be recalled. [ VIDEO ] ### Easing Curve Summary Cubic-bezier curve notation is the standard way to express easing curves. [IBM Motion Package](https://github.com/IBM/carbon-elements/tree/master/packages/motion) has the easing curves stored as tokens for fast access. | Easing | Productive | Expressive | |-----------------|---------------------------------|---------------------------------| | Standard easing | cubic-bezier(0.2, 0, 0.38, 0.9) | cubic-bezier(0.4, 0.14, 0.3, 1) | | Entrance easing | cubic-bezier(0, 0, 0.38, 0.9) | cubic-bezier(0, 0, 0.3, 1) | | Exit easing | cubic-bezier(0.2, 0, 1, 0.9) | cubic-bezier(0.4, 0.14, 1, 1) | ## Duration Duration is calculated based on the style and size of the motion. Among the two motion styles, **productive** motion is significantly faster than **expressive** motion. Motion’s duration should be dynamic based on the size of the animation - the larger the change in distance (traveled) or size (scaling) of the element, the longer the animation takes. <grid-wrapper col_lg="12" flex="true"> <do-dont-example correct="true" full_width="true" label="Duration contrast between a taller and a shorter component."> `vimeo: https://vimeo.com/310582312` </do-dont-example> </grid-wrapper> When custom duration is possible, please use the [Motion Generator](https://ibm.github.io/motion/) to get the customized duration calculated for you element. We uses a non-linear duration scale to achieve better perceived consistency across all distances. <grid-wrapper col_lg="8" flex="true" bleed="true"> <clickable-tile title="Motion Generator" href="https://ibm.github.io/motion/" type="resource" > </clickable-tile> </grid-wrapper> We are working on making dynamic duration a build-in feature for all Carbon components. Currently, we offer two static values as tokens for easier implementation. | Style | Token | Value | |-----------------|---------------------------------|---------------------------------| | Productive | $transition--base | 100ms | | Expressive | $transition--expansion | 150ms |

39.859091

352

0.675562

eng_Latn

0.940764

e97b346bba57b370a569aaafe4d5908f5d5ec86a

1,298

md

Markdown

_posts/2019-02-19-IntegratedN=8ThreeLoopFourPoint.md

Amplitudes/amplitudes

eaf13483194c21a6f45ea701410d8771d8ab071b

[ "MIT" ]

null

_posts/2019-02-19-IntegratedN=8ThreeLoopFourPoint.md

Amplitudes/amplitudes

eaf13483194c21a6f45ea701410d8771d8ab071b

[ "MIT" ]

null

_posts/2019-02-19-IntegratedN=8ThreeLoopFourPoint.md

Amplitudes/amplitudes

eaf13483194c21a6f45ea701410d8771d8ab071b

[ "MIT" ]

2

2020-09-15T13:13:03.000Z

2022-02-21T13:34:23.000Z

--- title: Four-graviton scattering to three loops in N=8 supergravity excerpt: Paper and Mathematica expressions. header: teaser: 3loopN8Integrals.png overlay_color: "#5e616c" overlay_image: 3loopN8Integrals.png overlay_filter: .6 categories: - amplitudes tags: - amplitudes - three-loop - N=8 SG - mathematica - four-point author: John_Joseph pinned: true --- {% include base_path %} # Link: Paper and Mathematica expressions. * [Four-graviton scattering to three loops in N=8 supergravity](https://arxiv.org/abs/1902.07221) * [Mathematica expressions](https://arxiv.org/src/1902.07221v1/anc) # Author(s): Johannes M. Henn, Bernhard Mistlberger # Abstract: We compute the three-loop scattering amplitude of four gravitons in N=8 supergravity. Our results are analytic formulae for a Laurent expansion of the amplitude in the regulator of dimensional regularisation. The coefficients of this series are closed formulae in terms of well-established harmonic poly-logarithms. Our results display a remarkable degree of simplicity and represent an important stepping stone in the exploration of the structure of scattering amplitudes. In particular, we observe that to this loop order the four graviton amplitude is given by uniform weight 2L functions, where L is the loop order.

40.5625

619

0.788136

eng_Latn

0.972889

e97b9cf335c98d419be9a6f579fb255fa425d696

133

md

Markdown

README.md

tonyonodi/reddit-comments

e5cd56d38036d90c24fdf027f5ead79a2a336f8c

[ "MIT" ]

null

README.md

tonyonodi/reddit-comments

e5cd56d38036d90c24fdf027f5ead79a2a336f8c

[ "MIT" ]

null

README.md

tonyonodi/reddit-comments

e5cd56d38036d90c24fdf027f5ead79a2a336f8c

[ "MIT" ]

null

Back to the Comments (reddit) ==================== This is a fork of Back to the Comments (Hacker News) intended to work on reddit.

26.6

80

0.639098

eng_Latn

0.995244