SEARCH · Search NASA

Results for “user”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 55 records · Page 3

All sources NASA NTRS DOE OSTI

NASA NTRS2010

Reinventing User Applications for Mission Control

In 2006, NASA Ames Research Center's (ARC) Intelligent Systems Division, and NASA Johnson Space Centers (JSC) Mission Operations Directorate (MOD) began a collaboration to move user applications for JSC's mission control center to a new software architecture, intended to replace the existing user applications being used for the Space Shuttle and the International Space Station. It must also carry NASA/JSC mission operations forward to the future, meeting the needs for NASA's exploration programs beyond low Earth orbit. Key requirements for the new architecture, called Mission Control Technologies (MCT) are that end users must be able to compose and build their own software displays without the need for programming, or direct support and approval from a platform services organization. Developers must be able to build MCT components using industry standard languages and tools. Each component of MCT must be interoperable with other components, regardless of what organization develops them. For platform service providers and MOD management, MCT must be cost effective, maintainable and evolvable. MCT software is built from components that are presented to users as composable user objects. A user object is an entity that represents a domain object such as a telemetry point, a command, a timeline, an activity, or a step in a procedure. User objects may be composed and reused, for example a telemetry point may be used in a traditional monitoring display, and that same telemetry user object may be composed into a procedure step. In either display, that same telemetry point may be shown in different views, such as a plot, an alpha numeric, or a meta-data view and those views may be changed live and in place. MCT presents users with a single unified user environment that contains all the objects required to perform applicable flight controller tasks, thus users do not have to use multiple applications, the traditional boundaries that exist between multiple heterogeneous applications disappear, leaving open the possibility of new operations concepts that are not constrained by the traditional applications paradigm.

Trimble, Jay Phillip↗

NASA NTRSDate not supplied

Informing Wildfire Needs: The Expanded User Interface of NASA's Fire Information for Resource Management System (Firms)

As the global community continues to experience, and respond to, living in a changing environment, access to tools, technologies, and timely data utilized by an increasingly diverse set of stakeholders is increasing. This year, 2023, has thus far seen an unprecedented number of extreme events, increasingly driven by changes in the climate and a strong 2023 ENSO pattern. In Canada, a record number of wildfires, and associated weather events, evacuations, and infrastructure and habitat destruction has taken place, and is ongoing. Large swaths of Greece have experienced similar wildfire destruction. Most recently, Maui has experienced destructive wildfires, and early 2023 saw massive wildfires in Chile. NASA's Fire Information for Resource Management System, or FIRMS, has a fifteen-year history of providing timely and comprehensive data and information on wildfires to stakeholders. FIRMS was initially developed in 2007 by the University of Maryland, with funds from NASA's Applied Sciences Program and the United Nations Food and Agriculture Organization (UN FAO), to provide near real-time active fire Locations to natural resource managers that faced challenges obtaining timely satellite-derived fire information. FIRMS has consistently evolved to address the needs of stakeholders Living in a changing environment; in 2012 it transitioned to NASA LANCE and in 2021 through a partnership between NASA and the US Forest Service, an updated version of FIRMS was released for the US and Canada. As NASA and other federal agencies continue to accelerate Open Science through integrated efforts such as the Year of Open Science, the provision of readily discoverable, findable, accessible, interoperable, reusable data represents a major focus to facilitate equitable outcomes. FIRMS supports this acceleration in Open Science by continuing to provision data and information for its traditional user base, while addressing the novel user needs of an increasingly diverse set of stakeholders seeking robust, reliable, transparently generated data and information. Increasingly, FIRMS is utilized by citizen scientists and individuals directly affected by wildfires - through evacuations, risks to structures/homes, poor air quality. etc. FIRMS has also been Leveraged to detect and assess the impacts resulting from ongoing conflicts. This further highlights the multi-faceted impacts of wildfires and other events. In the Fall of 2023, FIRMS will release an expanded User Interface (UI). This interface captures and reflects the needs of, and input from, a multitude of users. These users range from federal agency representatives to non-government organizations to the private sector to citizen science entities. To respond to this expansive and diverse user need base, the updated FIRMS UI will capture a range of features to support those beginning to explore the range of data and tools available to inform wildfire awareness and knowledge. These users are supported through a Basic Mode interface, furnishing access to a light set of functionalities that provision straight-forward, readily usable information and data, and ingestible knowledge. The Advanced Mode interface supports those stakeholder groups already proficient in navigating FIRMS. These stakeholders, representing fire managers and others, perform active fire management and tactical wildfire response activities. For these stakeholders, additional datasets have been included which require in-depth knowledge of both the utility as well as the caveats of such datasets. Additional functionalities have also been embedded to aid specific user queries. The expanded UI will introduce a new Experimental Mode. The focus of this UI will be to support the provision of emerging and innovative datasets that are in development for review and comment by the user community Examples include post-fire products generated by NASA's Earth Information System (EIS) Fire. This presentation will provide an overview of the expanded FIRMS UI. We will discuss how this UI is designed to be scalable and support the unique needs of an expanding and diverse user base. We will highlight key features, elements, and datasets, and describe how user needs have informed and guided the design of the UI. We will also share recent use cases to convey, and increase awareness, among conference participants. As the global community faces more extreme wildfires, due to climate variability and change, there is an increased need for reliable data to inform, manage, and mitigate the impacts of these events. Through this work, NASA FIRMS is striving to level the playing field, by making information accessible to all; from policy makers to the private sector to historically marginalized communities. In doing so, NASA is promoting the all-hands-on-deck response needed to minimize the impacts of wildfires and harness the strengths of open science to address the greatest environmental challenge faced.

Jenny Hewson↗

NASA NTRS1986

Intelligent user interface concept for space station

The space station computing system must interface with a wide variety of users, from highly skilled operations personnel to payload specialists from all over the world. The interface must accommodate a wide variety of operations from the space platform, ground control centers and from remote sites. As a result, there is a need for a robust, highly configurable and portable user interface that can accommodate the various space station missions. The concept of an intelligent user interface executive, written in Ada, that would support a number of advanced human interaction techniques, such as windowing, icons, color graphics, animation, and natural language processing is presented. The user interface would provide intelligent interaction by understanding the various user roles, the operations and mission, the current state of the environment and the current working context of the users. In addition, the intelligent user interface executive must be supported by a set of tools that would allow the executive to be easily configured and to allow rapid prototyping of proposed user dialogs. This capability would allow human engineering specialists acting in the role of dialog authors to define and validate various user scenarios. The set of tools required to support development of this intelligent human interface capability is discussed and the prototyping and validation efforts required for development of the Space Station's user interface are outlined.

Comer, Edward↗

NASA NTRS1992

Integrating a local database into the StarView distributed user interface

A distributed user interface to the Space Telescope Data Archive and Distribution Service (DADS) known as StarView is being developed. The DADS architecture consists of the data archive as well as a relational database catalog describing the archive. StarView is a client/server system in which the user interface is the front-end client to the DADS catalog and archive servers. Users query the DADS catalog from the StarView interface. Query commands are transmitted via a network and evaluated by the database. The results are returned via the network and are displayed on StarView forms. Based on the results, users decide which data sets to retrieve from the DADS archive. Archive requests are packaged by StarView and sent to DADS, which returns the requested data sets to the users. The advantages of distributed client/server user interfaces over traditional one-machine systems are well known. Since users run software on machines separate from the database, the overall client response time is much faster. Also, since the server is free to process only database requests, the database response time is much faster. Disadvantages inherent in this architecture are slow overall database access time due to the network delays, lack of a 'get previous row' command, and that refinements of a previously issued query must be submitted to the database server, even though the domain of values have already been returned by the previous query. This architecture also does not allow users to cross correlate DADS catalog data with other catalogs. Clearly, a distributed user interface would be more powerful if it overcame these disadvantages. A local database is being integrated into StarView to overcome these disadvantages. When a query is made through a StarView form, which is often composed of fields from multiple tables, it is translated to an SQL query and issued to the DADS catalog. At the same time, a local database table is created to contain the resulting rows of the query. The returned rows are displayed on the form as well as inserted into the local database table. Identical results are produced by reissuing the query to either the DADS catalog or to the local table. Relational databases do not provide a 'get previous row' function because of the inherent complexity of retrieving previous rows of multiple-table joins. However, since this function is easily implemented on a single table, StarView uses the local table to retrieve the previous row. Also, StarView issues subsequent query refinements to the local table instead of the DADS catalog, eliminating the network transmission overhead. Finally, other catalogs can be imported into the local database for cross correlation with local tables. Overall, it is believe that this is a more powerful architecture for distributed, database user interfaces.

Silberberg, D. P.↗

NASA NTRS1995

A user-system interface agent

Agent-based technologies answer to several challenges posed by additional information processing requirements in today's computing environments. In particular, (1) users desire interaction with computing devices in a mode which is similar to that used between people, (2) the efficiency and successful completion of information processing tasks often require a high-level of expertise in complex and multiple domains, (3) information processing tasks often require handling of large volumes of data and, therefore, continuous and endless processing activities. The concept of an agent is an attempt to address these new challenges by introducing information processing environments in which (1) users can communicate with a system in a natural way, (2) an agent is a specialist and a self-learner and, therefore, it qualifies to be trusted to perform tasks independent of the human user, and (3) an agent is an entity that is continuously active performing tasks that are either delegated to it or self-imposed. The work described in this paper focuses on the development of an interface agent for users of a complex information processing environment (IPE). This activity is part of an on-going effort to build a model for developing agent-based information systems. Such systems will be highly applicable to environments which require a high degree of automation, such as, flight control operations and/or processing of large volumes of data in complex domains, such as the EOSDIS environment and other multidisciplinary, scientific data systems. The concept of an agent as an information processing entity is fully described with emphasis on characteristics of special interest to the User-System Interface Agent (USIA). Issues such as agent 'existence' and 'qualification' are discussed in this paper. Based on a definition of an agent and its main characteristics, we propose an architecture for the development of interface agents for users of an IPE that is agent-oriented and whose resources are likely to be distributed and heterogeneous in nature. The architecture of USIA is outlined in two main components: (1) the user interface which is concerned with issues as user dialog and interaction, user modeling, and adaptation to user profile, and (2) the system interface part which deals with identification of IPE capabilities, task understanding and feasibility assessment, and task delegation and coordination of assistant agents.

Wakim, Nagi T.↗

NASA NTRS1997

Computer-Based Tools for Evaluating Graphical User Interfaces

The user interface is the component of a software system that connects two very complex system: humans and computers. Each of these two systems impose certain requirements on the final product. The user is the judge of the usability and utility of the system; the computer software and hardware are the tools with which the interface is constructed. Mistakes are sometimes made in designing and developing user interfaces because the designers and developers have limited knowledge about human performance (e.g., problem solving, decision making, planning, and reasoning). Even those trained in user interface design make mistakes because they are unable to address all of the known requirements and constraints on design. Evaluation of the user inter-face is therefore a critical phase of the user interface development process. Evaluation should not be considered the final phase of design; but it should be part of an iterative design cycle with the output of evaluation being feed back into design. The goal of this research was to develop a set of computer-based tools for objectively evaluating graphical user interfaces. The research was organized into three phases. The first phase resulted in the development of an embedded evaluation tool which evaluates the usability of a graphical user interface based on a user's performance. An expert system to assist in the design and evaluation of user interfaces based upon rules and guidelines was developed during the second phase. During the final phase of the research an automatic layout tool to be used in the initial design of graphical inter- faces was developed. The research was coordinated with NASA Marshall Space Flight Center's Mission Operations Laboratory's efforts in developing onboard payload display specifications for the Space Station.

Moore, Loretta A.↗

NASA NTRS1975

CARETS: A prototype regional environmental information system. Volume 12: User evaluation of experimental land use maps and related products from the central Atlantic test site

The user interaction and evaluation phase of the USGS/NASA Central Atlantic Regional Ecological Test Site was designed to obtain the input of local, regional, State, and Federal agency users of land-resource information into the development, of a regional information system; to provide users with assistance and data resulting from CARETS research; and to have user. organizations evaluate to what extent the CARETS products meet their needs. The evaluation of CARETS land use and related products revealed that most user agencies interviewed, at all governmental levels, require more detailed data than that provided by the CARETS project. Few agencies found utility in the generalized ERTS Level I land--use maps. Level II data, though reported valuable by several users, was generally considered of secondary utility by most users. The products considered most useful by users at all levels were the high--altitude color-infrared photographs and the USGS orthophotoquads. Recommendations resulting from the evaluation reflect the need to establish a flexible and reliable system for providing more detailed raw and processed land-resource information as well as the need to improve the methods of making information available to users.

Land-use planning↗

NASA NTRS1987

User engineering: A new look at system engineering

User Engineering is a new System Engineering perspective responsible for defining and maintaining the user view of the system. Its elements are a process to guide the project and customer, a multidisciplinary team including hard and soft sciences, rapid prototyping tools to build user interfaces quickly and modify them frequently at low cost, and a prototyping center for involving users and designers in an iterative way. The main consideration is reducing the risk that the end user will not or cannot effectively use the system. The process begins with user analysis to produce cognitive and work style models, and task analysis to produce user work functions and scenarios. These become major drivers of the human computer interface design which is presented and reviewed as an interactive prototype by users. Feedback is rapid and productive, and user effectiveness can be measured and observed before the system is built and fielded. Requirements are derived via the prototype and baselined early to serve as an input to the architecture and software design.

Mclaughlin, Larry L.↗

NASA NTRS2014

Sentiment of Search: KM and IT for User Expectations

User perceived value is the number one indicator of a successful implementation of KM and IT collaborations. The system known as "Search" requires more strategy and workflow that a mere data dump or ungoverned infrastructure can provide. Monitoring of user sentiment can be a driver for providing objective measures of success and justifying changes to the user interface. The dynamic nature of information technology makes traditional usability metrics difficult to identify, yet easy to argue against. There is little disagreement, however, on the criticality of adapting to user needs and expectations. The Systems Usability Scale (SUS), developed by John Brook in 1986 has become an industry standard for usability engineering. The first phase of a modified SUS, polls the sentiment of representative users of the JSC Search system. This information can be used to correlate user determined value with types of information sought and how the system is (or is not) meeting expectations. Sentiment analysis by way of the SUS assists an organization in identification and prioritization of the KM and IT variables impacting user perceived value. A secondary, user group focused analysis is the topic of additional work that demonstrates the impact of specific changes dictated by user sentiment.

Berndt, Sarah Ann↗

NASA NTRS2019

Integrated Analysis of Multiple User Metrics - A “Sequel”; and Introducing the Google Analytic

For decades, the Goddard Earth Sciences Data and Information Services Center (GES DISC) has archived and distributed enormous volumes of NASA Earth science data (accompanied with many developed tools and services) to various research/applications communities and the general public. Being “immersed” in the Big Data era, we have inevitably faced the challenges of our continually increasing archived data in both volume and variety, as well as enhanced user needs and demands. In recent years, we have actively analyzed different types of user metrics, such as operational distribution metrics (recording numbers of distinct users and downloaded data files, size of distributed data volume): user publication metrics (mining info from our Giovanni users’ publications): and Bugzilla metrics (collecting info from user questions or feedback from user assistance tickets). Such metrics have helped us achieve a better understanding of user needs, demands, characteristics, and behaviors, which has then helped us improve our user services. Now we will present a “Sequel” of integrated analysis of multiple metrics at the GES DISC by introducing and adding one new kind of metrics acquired via utilizing our recently implemented Google Analytic 360 suite. Several “newer” reports, e.g., “What web site features and links are the most popular (and least)?” and “What are the top 25 dataset Keyword searches?” retrieved from this new metrics set will be presented, along with the aforementioned “traditional” metrics results.

Shie, Chung-Lin↗

NASA NTRS1973

Study of data collection platform concepts: Data collection system user requirements

The overall purpose of the survey was to provide real world data on user requirements. The intent was to assess data collection system user requirements by questioning actual potential users rather than speculating on requirements. The end results of the survey are baseline requirements models for both a data collection platform and a data collection system. These models were derived from the survey results. The real value of these models lies in the fact that they are based on actual user requirements as delineated in the survey questionnaires. Some users desire data collection platforms of small size and light weight. These sizes and weights are beyond the present state of the art. Also, the survey provided a wealth of information on the nature and constituency of the data collection user community as well as information on user applications for data collection systems. Finally, the data sheds light on the generalized platform concept. That is, the diversity of user requirements shown in the data indicates the difficulty that can be anticipated in attempting to implement such a concept.

Source record↗

NASA NTRS1976

Phase 2 STS new user development program. Volume 1: Executive summary

A methodology for developing new users for STS other than NASA and DoD, thereby maximizing the use of the STS system was developed. The approach to user development, reflected in the implementation plan, and attendant informational material to be used were evaluated by conducting a series of test cases with selected user organizations. These test case organizations were, in effect, used as consultants to evaluate the effectiveness, the needs, the completeness, and the adequacy of the user development approach and informational material. The selection of the test cases provided a variety of potential STS users covering industry, other government agencies, and the educational sector. The test cases covered various use areas and provided a mix of user organization types. A summary of the actual test cases conducted is given. The conduct of the test cases verified the general approach of the implementation plan, the validity of the user development strategy prepared for each test case organization and the effectiveness of the STS basic and user customized informational material.

Mcdowell, J. R.↗

NASA NTRS1976

Phase 2 STS new user development program. Volume 4: Guidance/instructions for representatives

The overall STS New User Development (NUD) Function is shown. The user development function is directly responsible for implementing the strategy derived to develop a specific, prospective new user. The burden of actually developing the user falls on the NUD representative, and the success of his user contacts will depend upon how well he is prepared to interface with the user. The guidance/instructions as to what a NUD representative needs to know about the prospective user, and the type of data he should provide when calling on a potential user, are presented.

Mcdowell, J. R.↗

NASA NTRS1980

Seasat data applications by commercial users

The Seasat Program was initiated as a proof-of-concept mission to evaluate the effectiveness of a study of remotely sensed oceanographic phenomena from a satellite platform. From its inception the Seasat Program has been user-oriented. The user comprised three major segments of the ocean community, including academic users, users within various government agencies, and commercial users. Commercial users represent a broad spectrum of commercial marine industries. The commercial users proposed to NASA to carry out a pilot demonstration to assess the utility of Seasat data in the private sector. The commercial users' program is considered along with case studies that utilize Seasat data, and aspects of real-time system operation. Attention is given to the potential value of an employment of synthetic aperture radar, the altimeter, the scatterometer, and the scanning multichannel microwave radiometer.

Montgomery, D. R.↗

NASA NTRS1990

Compensating user position for GPS ephemeris error

A method for canceling the effect of GPS ephemeris error on user position is proposed. In this method, the baseline vectors from the reference stations to the user are estimated without adjusting the GPS ephemeris. The user position is computed by adjustment using differenced data from the user and each station separately and averaging the results with weights inversely proportional to the lengths of the baselines. Alternatively, the differenced data can be averaged in a similar manner before the user position is estimated. The averaging procedure cancels most of the ephemeris error because the error is proportional to the length of the baseline. A numerical simulation is performed to demonstrate and evaluate the method. Two reference stations with perfectly known locations are assumed to be placed several hundred kilometers apart. A user receiver with a poorly known location is located between the stations. The user positions are first estimated separately using data from the user and each station and then averaged. The averaging reduces the error by about one order of magnitude.

Wu, J. T.↗

NASA NTRS1994

FAST User Guide

The Flow Analysis Software Toolkit, FAST, is a software environment for visualizing data. FAST is a collection of separate programs (modules) that run simultaneously and allow the user to examine the results of numerical and experimental simulations. The user can load data files, perform calculations on the data, visualize the results of these calculations, construct scenes of 3D graphical objects, and plot, animate and record the scenes. Computational Fluid Dynamics (CFD) visualization is the primary intended use of FAST, but FAST can also assist in the analysis of other types of data. FAST combines the capabilities of such programs as PLOT3D, RIP, SURF, and GAS into one environment with modules that share data. Sharing data between modules eliminates the drudgery of transferring data between programs. All the modules in the FAST environment have a consistent, highly interactive graphical user interface. Most commands are entered by pointing and'clicking. The modular construction of FAST makes it flexible and extensible. The environment can be custom configured and new modules can be developed and added as needed. The following modules have been developed for FAST: VIEWER, FILE IO, CALCULATOR, SURFER, TOPOLOGY, PLOTTER, TITLER, TRACER, ARCGRAPH, GQ, SURFERU, SHOTET, and ISOLEVU. A utility is also included to make the inclusion of user defined modules in the FAST environment easy. The VIEWER module is the central control for the FAST environment. From VIEWER, the user can-change object attributes, interactively position objects in three-dimensional space, define and save scenes, create animations, spawn new FAST modules, add additional view windows, and save and execute command scripts. The FAST User Guide uses text and FAST MAPS (graphical representations of the entire user interface) to guide the user through the use of FAST. Chapters include: Maps, Overview, Tips, Getting Started Tutorial, a separate chapter for each module, file formats, and system administration.

Walatka, Pamela P.↗

NASA NTRS1998

Collaborative Arrival Planning: Data Sharing and User Preference Tools

Air traffic growth and air carrier economic pressures have motivated efforts to increase the flexibility of the air traffic management process and change the relationship between the air traffic control service provider and the system user. One of the most visible of these efforts is the U.S. government/industry "free flight" initiative, in which the service provider concentrates on safety and cross-airline fairness, and the user on their business objectives and operating preferences, including selecting their own path and speed in real-time. In the terminal arrival phase of flight, severe restrictions and rigid control are currently placed on system users, typically without regard for individual user operational preferences. Airborne delays applied to arriving aircraft into capacity constrained airports are imposed on a first-come, first-serve basis, and thus do not allow the system user to plan for or prioritize late arrivals, or to economically optimize their arrival sequence. A central tenant of the free-flight operating paradigm is collaboration between service providers and users in reaching air traffic management decisions. Such collaboration would be particularly beneficial to an airline's "hub" operation, where off-schedule arrival aircraft are a consistent problem, as they cause serious air-port ramp difficulties, rippling airline scheduling effects, and result in large economic inefficiencies. Greater collaboration can also lead to increased airport capacity and decrease the severity of over-capacity rush periods. In the NASA Collaborative Arrival Planning (CAP) project, both independent exchange of real-time data between the service provider and system user and collaborative decision support tools are addressed. Data exchange of real-time arrival scheduling, airspace management, and air carrier fleet data between the FAA service provider and an air carrier is being conducted and evaluated. Collaborative arrival decision support tools to allow intra-airline arrival preferences are being developed and simulated. The CAP project is part of and leveraged from the NASA/FAA Center TRACON Automation System (CTAS), a fielded set of decision support tools that provide computer generated advisories for both enroute and terminal area controllers to manage and control arrival traffic more efficiently. In this paper, the NASA Collaborative Arrival Planning project is outlined and recent results detailed, including the real-time use of CTAS arrival scheduling data by a major air carrier and simulations of tactical and strategic user preference decision support tools.

Zelenka, Richard E.↗

NASA NTRS2003

Discrete Abstractions of Hybrid Systems: Verification of Safety and Application to User-Interface Design

Human interaction with a complex control system involves the user, the automation’s discrete mode logic, and the underlying continuous dynamics of the physical system. The user-interface of such systems always displays a reduced set of information about the entire system. Designing interfaces such that all the pertinent information is available and assuring that this information is correct is important for any user-interface, but especially so for safety-critical systems such as automotive systems and autopilots. Here we describe a methodology for the analysis of hybrid control systems that incorporate user interaction, with the goal of assuring that the information provided to the user is correct. That is, the user-interface must contain all information necessary to safely complete a desired procedure or task. We begin with a hybrid system model which incorporates discrete mode logic as well as nonlinear continuous dynamics. Using a hybrid computational tool for reachability, we find the largest region of the state-space in which we can guarantee the state of the system can always remain – this is the safe region of operation. By implementing a controller for safety which arises from this computation, we mathematically guarantee that this safe region is invariant, meaning that the system will always remain within the safe region if the determined controller is used on the boundary of the safe region. Verification within a hybrid framework allows us to account for the continuous dynamics underlying the discrete representations displayed to the user. Using the computed invariant regions as discrete states, we can abstract a discrete event system from this hybrid system with safety restrictions. This abstraction can be used to determine what information must be provided on the display. Furthermore, in cases in which an interface already exists, the abstraction provides the necessary input into existing interface verification methods. We provide two examples: a car traveling through a yellow light at an intersection and an aircraft autopilot in an automatic landing/go-around maneuver. The examples demonstrate the applicability of this methodology to hybrid systems that have operational constraints we can pose in terms of safety. This methodology differs from existing work in hybrid system verification in that we directly account for the user’s interactions with the system.

Meeko Oishi↗