Description of Experiment Sample Clauses

Description of Experiment. In the first user experiment, on Mobile Journalism, 12 participants were asked to join a role-play of a fictive local media company. The play aimed to evoke a context where participants experience the challenge of capturing compelling news stories and where they can experience newsroom time pressure. Four teams were asked to create two short news bulletins storifying capturing citizens thoughts on the current and the future City. All participants got an introductive course on mobile journalism and storytelling. The newsroom editors guided the remote journalists using a live chat channel, provided via a mobile application developed by VRT. Captured videos were sent to the newsroom using the FLAME platform. Figure 1. The journalist as a designer. Creating tangible conversation openers used in interviews (Photo FLAME , 2018 ). Figure
Sample 1
AutoNDA by SimpleDocs
Description of Experiment. The PMM offers an experience in which “my content is always available” from anywhere (within the smart city), from any device and for anyone with access to personal media server (typically family members). In our experiment we presented two scenarios: • PMM distribution in walking areas in Barcelona (see Figure 9): the main goal is to validate how users can be able to start, stop and resume the playback of audio/video content from another place with another device. The consumption of the media content continues while the user is walking in the Smart City without losing bookmarks and preferences; • PMM for multiple concurrent streams within the Smart City (see Figure 10): the QoE offered by the platform is tested with multiple users, dislocated along the smart city area, accessing to the same personal contents. FLAME-empowered Smart City Infrastructure FLAME-empowered Smart City Infrastructure The PMM experiments over the FLAME platform evaluate functions for media distribution that are suitable for serving dispersed endpoints in the FLAME-empowered Smart City. Indeed, the evaluation is focused on how FLAME allows to go beyond the traditional Content Delivery Network (CDN) architectures currently available for media distribution over IP. As shown in Figure 11, the PMM Service Function Chain (SFC), when the service is at first deployed, consists of a Personalised Media Origin Server (based on PLEX) deployed in the core data centre of the FLAME infrastructure in Barcelona. Initially, the Origin Server is active and connected through the FLIPS routing capability in order to be reachable by the Access Points of the FLAME platform in the area of Pere IV district. Replicas of the Origin server are placed but not connected into “gateworks” clusters (street cabinet units for edge computing). The PLEX Origin Server periodically sends data about streaming statistics (bandwidth, number of active streaming, type of active streaming, etc.) to FLAME’s CLMC.
Sample 1
Description of Experiment. The validation scenario experiments take place on Millennium Square in Bristol, UK, where a few famous Bristolians are present in the form of life-sized bronze statues. The story is acted out on different AR stages. These AR stages are mapped to specific locations on the Millennium Square with the help of GPS locations and AR markers. When the user gets into proximity of one of these locations, the stage is downloaded and visualized as soon as the corresponding AR marker is found. The AR markers are used to properly orient the stage relative to the real environment, which brings together the digital and physical world.
Sample 1
Description of Experiment. The Game Technology Center (GTC) at ETH Zurich, Switzerland, has been developing a team-based augmented reality (AR) urban arena game called Gnome Trader to validate the FLAME platform. The goal of the game is to collect as many tree seeds as possible for your team. Tree seeds can be gained either by planting trees in your AR garden and harvesting them once they’re fully grown, or by going to the virtual AR gnome shops distributed across Millennium Square to buy tree seeds. Each tree has its own associated 3D model, which is downloaded when its seed is planted by a player. A planted tree will trigger the download for every other player. Multiple players requesting to download the same 3D asset from the server will trigger multicasting. Some impressions of the game can be seen in Figure 22.
Sample 1
Description of Experiment. Notes: In the triple dictator game, Players B do not have a decision to make. They, rather than Players A, choose a transfer amount in the modified dictator game. 0.5 0.4 0.3 0.2 0.1 Cox Trust Our Trust 0.5 0.4 0.3 0.2 0.1 Cox Dictator Our Dictator Study Country Fraction Return Fraction Returned Ratio BDM Students Sent y/tx y/x Limited Strategy Space Equal Endowments Double Blind Strategy Method Multiplication of Transfer Comments Xxxx et al. (1995) USA 0.52 0.3 0.9 - X X X 3x No Ashraf et al. (2006)1 Russia South Africa USA 0.1 0.49 0.29 0.80 X X 3x X 0.11 0.43 0.27 0.73 X X 3x X 0.09 0.41 0.23 0.58 X X 3x X Xxxxx et al. Russia 0.03 0.51 0.40 1.19 3x X (2004) Bs asked to 2 predict transfer Xxxxx (2006) South Africa N/A 0.33 0.23 0.69 X High School X 3x X Xxxxxxxxx & Xxxx (2007) Tanzania 0 0.56 0.46 1.38 X X X 3x X Xxxxxxxxx (2000) Kenya 0 0.44 0.18
Sample 1

Related to Description of Experiment

  • Description of Services A description of Google Workspace for Education Service provided by Google is set forth in the Services Summary located at xxxxx://xxxxxxxxx.xxxxxx.xxx/terms/user_features.html.

  • LIMITATIONS ON REVERSE ENGINEERING, DECOMPILATION AND DISASSEMBLY You may not reverse engineer, decompile, or disassemble the Software, except and only to the extent that such activity is expressly permitted by applicable law notwithstanding this limitation.

  • Description of Deliverables The Contractor shall Perform as set forth in Exhibit A.

  • Detailed Description of Services / Statement of Work Describe fully the services that Contractor will provide, or add and attach Exhibit B to this Agreement.

  • Incorporation of Software Code I agree that I will not incorporate into any Company software or otherwise deliver to Company any software code licensed under the GNU General Public License or Lesser General Public License or any other license that, by its terms, requires or conditions the use or distribution of such code on the disclosure, licensing, or distribution of any source code owned or licensed by Company except in strict compliance with Company’s policies regarding the use of such software.

  • Description of Work that has been omitted or

  • Resolution of Discrepancies In the event of any discrepancy between the information set forth in any report provided by the Custodian to the Company and any information contained in the books or records of the Company, the Company shall promptly notify the Custodian thereof and the parties shall cooperate to diligently resolve the discrepancy.

  • Description of the service 10.1.1 Automatic transfer service implies a transfer by the bank of the funds from the client’s account without further consent of the client, on the basis of fixed amount determined by the client in its application form or of information provided by the client’s creditor to the bank on the client’s debt. 10.1.2 The parties agree that the payment order created (generated) by the bank for the purposes of automatic transfer services shall have the legal force equal to the document having been printed on the paper and executed by the person(s) authorized to manage of the account. 10.1.3 The bank shall carry out the automatic transfer services in accordance with requirements and conditions stipulated in this agreement, the application on registration for automatic transfer service and the sources disseminated by the bank. 10.1.4 For the purposes of obtaining automatic transfer services the client shall apply to the bank with the application as per paragraph 1.2 of this agreement.

  • Description of Funding Techniques 6.2.1 The following are terms under which standard funding techniques shall be implemented for all transfers of funds to which the funding technique is applied in section 6.3.2 of this Agreement. Funding Technique Name Description Actual Clearance, ZBA - Same Day Payment The State shall request funds the same day it pays out funds, in accordance with the appropriate Federal agency cut-off time specified in Exhibit I. A Federal agency will deposit funds in a State account the same day as requested. The amount of the request shall be for the amount of funds that clear the State's account that day. This funding technique is interest neutral. Composite Clearance The State shall request funds such that they are deposited on the dollar-weighted average number of days required for funds to be paid out for a series of disbursements, in accordance with the clearance pattern specified in Exhibit II. The request shall be made in accordance with the appropriate Federal agency cut-off time specified in Exhibit I. The amount of the request shall be the sum of the payments issued in the series of disbursements. This funding technique is interest neutral. Pre-Issuance The State shall request funds such that they are deposited in a State account not more than three business days prior to the day the State makes a disbursement. The request shall be made in accordance with the appropriate Federal agency cut-off time specified in Exhibit I. The amount of the request shall be the amount the State expects to disburse. This funding technique is not interest neutral. 6.2.2 The following are terms under which funding techniques for administrative costs shall be implemented for all transfers of funds to which the funding technique is applied in section 6.3.2 of this Agreement. Funding Technique Name Description Actual Costs - Estimated Allocation - Monthly The State shall request funds once a month, such that they are deposited on the median day of the month, to fund the activity of the prior month. The request shall be made in accordance with the appropriate Federal agency cut-off time specified in Exhibit I. The amount of the request shall be an estimate based on the actual costs of the month distributed to the program according to the allocation of costs for the preceding six months. This funding technique is interest neutral. 6.2.3 The following are terms under which miscellaneous funding techniques shall be implemented for all transfers of funds to which the funding technique is applied in section 6.3.2 of this Agreement. There are currently no funding techniques listed in Section 6.2.3. 6.2.4 The following are terms under which State unique funding techniques shall be implemented for all transfers of funds to which the funding technique is applied in section 6.3.2 of this Agreement. There are currently no programs listed for Section 6.2.4.

  • Description of Service 2.9.1.1 BellSouth shall make available to <<customer_short_name>> LMU information with respect to Loops that are required to be unbundled under this Agreement so that <<customer_short_name>> can make an independent judgment about whether the Loop is capable of supporting the advanced services equipment <<customer_short_name>> intends to install and the services <<customer_short_name>> wishes to provide. LMU is a preordering transaction, distinct from <<customer_short_name>> ordering any other service(s). Loop Makeup Service Inquiries (LMUSI) and mechanized LMU queries for preordering LMU are likewise unique from other preordering functions with associated SIs as described in this Agreement. 2.9.1.2 BellSouth will provide <<customer_short_name>> LMU information consisting of the composition of the Loop material (copper/fiber); the existence, location and type of equipment on the Loop, including but not limited to digital loop carrier or other remote concentration devices, feeder/distribution interfaces, bridged taps, load coils, pair-gain devices; the Loop length; the wire gauge and electrical parameters. 2.9.1.3 BellSouth’s LMU information is provided to <<customer_short_name>> as it exists either in BellSouth's databases or in its hard copy facility records. BellSouth does not guarantee accuracy or reliability of the LMU information provided. 2.9.1.4 BellSouth’s provisioning of LMU information to the requesting CLEC for facilities is contingent upon either BellSouth or the requesting CLEC controlling the Loop(s) that serve the service location for which LMU information has been requested by the CLEC. The requesting CLEC is not authorized to receive LMU information on a facility used or controlled by another CLEC unless BellSouth receives a LOA from the voice CLEC (owner) or its authorized agent on the LMUSI submitted by the requesting CLEC. 2.9.1.5 <<customer_short_name>> may choose to use equipment that it deems will enable it to provide a certain type and level of service over a particular BellSouth Loop as long as that equipment does not disrupt other services on the BellSouth network. The determination shall be made solely by <<customer_short_name>> and BellSouth shall not be liable in any way for the performance of the advanced data services provisioned over said Loop. The specific Loop type (e.g., ADSL, HDSL, or otherwise) ordered on the LSR must match the LMU of the Loop reserved taking into consideration any requisite line conditioning. The LMU data is provided for informational purposes only and does not guarantee <<customer_short_name>>’s ability to provide advanced data services over the ordered Loop type. Furthermore, the LMU information for Loops other than copper-only Loops (e.g., ADSL, UCL-ND, etc.) that support xDSL services, is subject to change at any time due to modifications and/or upgrades to BellSouth’s network. Except as set forth in Section 2.9.1.6, copper-only Loops will not be subject to change due to modification and/or upgrades to BellSouth’s network and will remain on copper facilities until the Loop is disconnected by <<customer_short_name>> or the End User, or until BellSouth retires the copper facilities via the FCC’s and any applicable Commission’s requirements. <<customer_short_name>> is fully responsible for any of its service configurations that may differ from BellSouth’s technical standard for the Loop type ordered. 2.9.1.6 If BellSouth retires its copper facilities using 47 C.F.R § 52.325(a) requirements; or is required by a governmental agency or regulatory body to move or replace copper facilities as a maintenance procedure, BellSouth will notify <<customer_short_name>>, according to the applicable network disclosure requirements. It will be <<customer_short_name>>’s responsibility to move any service it may provide over such facilities to alternative facilities. If <<customer_short_name>> fails to move the service to alternative facilities by the date in the network disclosure notice, BellSouth may terminate the service to complete the network change.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!