#injection moduling machine exporters | Explore Tumblr posts and blogs

foxandco94 · 4 years ago

Text

Airflow Clickhouse

Aspect calc. Aspect ratio calculator to get aspect ratio for your images or videos (4:3, 16:9, etc.).

Airflow Clickhouse Example

Airflow-clickhouse-plugin 0.6.0 Mar 13, 2021 airflow-clickhouse-plugin - Airflow plugin to execute ClickHouse commands and queries. Baluchon 0.0.1 Dec 19, 2020 A tool for managing migrations in Clickhouse. Domination 1.2 Sep 21, 2020 Real-time application in order to dominate Humans. Intelecy-pandahouse 0.3.2 Aug 25, 2020 Pandas interface for. I investigate how fast ClickHouse 18.16.1 can query 1.1 billion taxi journeys on a 3-node, 108-core AWS EC2 cluster. Convert CSVs to ORC Faster I compare the ORC file construction times of Spark 2.4.0, Hive 2.3.4 and Presto 0.214. Rev transcription career. We and third parties use cookies or similar technologies ('Cookies') as described below to collect and process personal data, such as your IP address or browser information. The world's first data engineering coding bootcamp in Berlin. Learn sustainable data craftsmanship beyond the AI-hype. Join our school and learn how to build and maintain infrastructure that powers data products, data analytics tools, data science models, business intelligence and machine learning s.

Airflow Clickhouse Connection

Package Name AccessSummary Updated jupyterlabpublic An extensible environment for interactive and reproducible computing, based on the Jupyter Notebook and Architecture. 2021-04-22httpcorepublic The next generation HTTP client. 2021-04-22jsondiffpublic Diff JSON and JSON-like structures in Python 2021-04-22jupyter_kernel_gatewaypublic Jupyter Kernel Gateway 2021-04-22reportlabpublic Open-source engine for creating complex, data-driven PDF documents and custom vector graphics 2021-04-21pytest-asynciopublic Pytest support for asyncio 2021-04-21enamlpublic Declarative DSL for building rich user interfaces in Python 2021-04-21onigurumapublic A regular expression library. 2021-04-21cfn-lintpublic CloudFormation Linter 2021-04-21aws-c-commonpublic Core c99 package for AWS SDK for C. Includes cross-platform primitives, configuration, data structures, and error handling. 2021-04-21nginxpublic Nginx is an HTTP and reverse proxy server 2021-04-21libgcryptpublic a general purpose cryptographic library originally based on code from GnuPG. 2021-04-21google-authpublic Google authentication library for Python 2021-04-21sqlalchemy-utilspublic Various utility functions for SQLAlchemy 2021-04-21flask-apschedulerpublic Flask-APScheduler is a Flask extension which adds support for the APScheduler 2021-04-21datadogpublic The Datadog Python library 2021-04-21cattrspublic Complex custom class converters for attrs. 2021-04-21argcompletepublic Bash tab completion for argparse 2021-04-21luarockspublic LuaRocks is the package manager for Lua modulesLuaRocks is the package manager for Lua module 2021-04-21srslypublic Modern high-performance serialization utilities for Python 2021-04-19pytest-benchmarkpublic A py.test fixture for benchmarking code 2021-04-19fastavropublic Fast read/write of AVRO files 2021-04-19cataloguepublic Super lightweight function registries for your library 2021-04-19zarrpublic An implementation of chunked, compressed, N-dimensional arrays for Python. 2021-04-19python-engineiopublic Engine.IO server 2021-04-19nuitkapublic Python compiler with full language support and CPython compatibility 2021-04-19hypothesispublic A library for property based testing 2021-04-19flask-adminpublic Simple and extensible admin interface framework for Flask 2021-04-19hyperframepublic Pure-Python HTTP/2 framing 2021-04-19pythonpublic General purpose programming language 2021-04-17python-regr-testsuitepublic General purpose programming language 2021-04-17pyamgpublic Algebraic Multigrid Solvers in Python 2021-04-17luigipublic Workflow mgmgt + task scheduling + dependency resolution. 2021-04-17libpython-staticpublic General purpose programming language 2021-04-17dropboxpublic Official Dropbox API Client 2021-04-17s3fspublic Convenient Filesystem interface over S3 2021-04-17furlpublic URL manipulation made simple. 2021-04-17sympypublic Python library for symbolic mathematics 2021-04-15spyderpublic The Scientific Python Development Environment 2021-04-15sqlalchemypublic Database Abstraction Library. 2021-04-15rtreepublic R-Tree spatial index for Python GIS 2021-04-15pandaspublic High-performance, easy-to-use data structures and data analysis tools. 2021-04-15poetrypublic Python dependency management and packaging made easy 2021-04-15freetdspublic FreeTDS is a free implementation of Sybase's DB-Library, CT-Library, and ODBC libraries 2021-04-15ninjapublic A small build system with a focus on speed 2021-04-15cythonpublic The Cython compiler for writing C extensions for the Python language 2021-04-15conda-package-handlingpublic Create and extract conda packages of various formats 2021-04-15condapublic OS-agnostic, system-level binary package and environment manager. 2021-04-15colorlogpublic Log formatting with colors! 2021-04-15bitarraypublic efficient arrays of booleans -- C extension 2021-04-15

Reverse Dependencies of apache-airflow

Clickhouse Icon

Digital recorder that transcribes to text. The following projects have a declared dependency on apache-airflow:

Clickhouse Download

acryl-datahub — A CLI to work with DataHub metadata

AGLOW — AGLOW: Automated Grid-enabled LOFAR Workflows

aiflow — AI Flow, an extend operators library for airflow, which helps AI engineer to write less, reuse more, integrate easily.

aircan — no summary

airflow-add-ons — Airflow extensible opertators and sensors

airflow-aws-cost-explorer — Apache Airflow Operator exporting AWS Cost Explorer data to local file or S3

airflow-bigquerylogger — BigQuery logger handler for Airflow

airflow-bio-utils — Airflow utilities for biological sequences

airflow-cdk — Custom cdk constructs for apache airflow

airflow-clickhouse-plugin — airflow-clickhouse-plugin - Airflow plugin to execute ClickHouse commands and queries

airflow-code-editor — Apache Airflow code editor and file manager

airflow-cyberark-secrets-backend — An Airflow custom secrets backend for CyberArk CCP

airflow-dbt — Apache Airflow integration for dbt

airflow-declarative — Airflow DAGs done declaratively

airflow-diagrams — Auto-generated Diagrams from Airflow DAGs.

airflow-ditto — An airflow DAG transformation framework

airflow-django — A kit for using Django features, like its ORM, in Airflow DAGs.

airflow-docker — An opinionated implementation of exclusively using airflow DockerOperators for all Operators

airflow-dvc — DVC operator for Airflow

airflow-ecr-plugin — Airflow ECR plugin

airflow-exporter — Airflow plugin to export dag and task based metrics to Prometheus.

airflow-extended-metrics — Package to expand Airflow for custom metrics.

airflow-fs — Composable filesystem hooks and operators for Airflow.

airflow-gitlab-webhook — Apache Airflow Gitlab Webhook integration

airflow-hdinsight — HDInsight provider for Airflow

airflow-imaging-plugins — Airflow plugins to support Neuroimaging tasks.

airflow-indexima — Indexima Airflow integration

airflow-notebook — Jupyter Notebook operator for Apache Airflow.

airflow-plugin-config-storage — Inject connections into the airflow database from configuration

airflow-plugin-glue-presto-apas — An Airflow Plugin to Add a Partition As Select(APAS) on Presto that uses Glue Data Catalog as a Hive metastore.

airflow-prometheus — Modern Prometheus exporter for Airflow (based on robinhood/airflow-prometheus-exporter)

airflow-prometheus-exporter — Prometheus Exporter for Airflow Metrics

airflow-provider-fivetran — A Fivetran provider for Apache Airflow

airflow-provider-great-expectations — An Apache Airflow provider for Great Expectations

airflow-provider-hightouch — Hightouch Provider for Airflow

airflow-queue-stats — An airflow plugin for viewing queue statistics.

airflow-spark-k8s — Airflow integration for Spark On K8s

airflow-spell — Apache Airflow integration for spell.run

airflow-tm1 — A package to simplify connecting to the TM1 REST API from Apache Airflow

airflow-util-dv — no summary

airflow-waterdrop-plugin — A FastAPI Middleware of Apollo(Config Server By CtripCorp) to get server config in every request.

airflow-windmill — Drag'N'Drop Web Frontend for Building and Managing Airflow DAGs

airflowdaggenerator — Dynamically generates and validates Python Airflow DAG file based on a Jinja2 Template and a YAML configuration file to encourage code re-usability

airkupofrod — Takes a deployment in your kubernetes cluster and turns its pod template into a KubernetesPodOperator object.

airtunnel — airtunnel – tame your Airflow!

apache-airflow-backport-providers-amazon — Backport provider package apache-airflow-backport-providers-amazon for Apache Airflow

apache-airflow-backport-providers-apache-beam — Backport provider package apache-airflow-backport-providers-apache-beam for Apache Airflow

apache-airflow-backport-providers-apache-cassandra — Backport provider package apache-airflow-backport-providers-apache-cassandra for Apache Airflow

apache-airflow-backport-providers-apache-druid — Backport provider package apache-airflow-backport-providers-apache-druid for Apache Airflow

apache-airflow-backport-providers-apache-hdfs — Backport provider package apache-airflow-backport-providers-apache-hdfs for Apache Airflow

apache-airflow-backport-providers-apache-hive — Backport provider package apache-airflow-backport-providers-apache-hive for Apache Airflow

apache-airflow-backport-providers-apache-kylin — Backport provider package apache-airflow-backport-providers-apache-kylin for Apache Airflow

apache-airflow-backport-providers-apache-livy — Backport provider package apache-airflow-backport-providers-apache-livy for Apache Airflow

apache-airflow-backport-providers-apache-pig — Backport provider package apache-airflow-backport-providers-apache-pig for Apache Airflow

apache-airflow-backport-providers-apache-pinot — Backport provider package apache-airflow-backport-providers-apache-pinot for Apache Airflow

apache-airflow-backport-providers-apache-spark — Backport provider package apache-airflow-backport-providers-apache-spark for Apache Airflow

apache-airflow-backport-providers-apache-sqoop — Backport provider package apache-airflow-backport-providers-apache-sqoop for Apache Airflow

apache-airflow-backport-providers-celery — Backport provider package apache-airflow-backport-providers-celery for Apache Airflow

apache-airflow-backport-providers-cloudant — Backport provider package apache-airflow-backport-providers-cloudant for Apache Airflow

apache-airflow-backport-providers-cncf-kubernetes — Backport provider package apache-airflow-backport-providers-cncf-kubernetes for Apache Airflow

apache-airflow-backport-providers-databricks — Backport provider package apache-airflow-backport-providers-databricks for Apache Airflow

apache-airflow-backport-providers-datadog — Backport provider package apache-airflow-backport-providers-datadog for Apache Airflow

apache-airflow-backport-providers-dingding — Backport provider package apache-airflow-backport-providers-dingding for Apache Airflow

apache-airflow-backport-providers-discord — Backport provider package apache-airflow-backport-providers-discord for Apache Airflow

apache-airflow-backport-providers-docker — Backport provider package apache-airflow-backport-providers-docker for Apache Airflow

apache-airflow-backport-providers-elasticsearch — Backport provider package apache-airflow-backport-providers-elasticsearch for Apache Airflow

apache-airflow-backport-providers-email — Back-ported airflow.providers.email.* package for Airflow 1.10.*

apache-airflow-backport-providers-exasol — Backport provider package apache-airflow-backport-providers-exasol for Apache Airflow

apache-airflow-backport-providers-facebook — Backport provider package apache-airflow-backport-providers-facebook for Apache Airflow

apache-airflow-backport-providers-google — Backport provider package apache-airflow-backport-providers-google for Apache Airflow

apache-airflow-backport-providers-grpc — Backport provider package apache-airflow-backport-providers-grpc for Apache Airflow

apache-airflow-backport-providers-hashicorp — Backport provider package apache-airflow-backport-providers-hashicorp for Apache Airflow

apache-airflow-backport-providers-jdbc — Backport provider package apache-airflow-backport-providers-jdbc for Apache Airflow

apache-airflow-backport-providers-jenkins — Backport provider package apache-airflow-backport-providers-jenkins for Apache Airflow

apache-airflow-backport-providers-jira — Backport provider package apache-airflow-backport-providers-jira for Apache Airflow

apache-airflow-backport-providers-microsoft-azure — Backport provider package apache-airflow-backport-providers-microsoft-azure for Apache Airflow

apache-airflow-backport-providers-microsoft-mssql — Backport provider package apache-airflow-backport-providers-microsoft-mssql for Apache Airflow

apache-airflow-backport-providers-microsoft-winrm — Backport provider package apache-airflow-backport-providers-microsoft-winrm for Apache Airflow

apache-airflow-backport-providers-mongo — Backport provider package apache-airflow-backport-providers-mongo for Apache Airflow

apache-airflow-backport-providers-mysql — Backport provider package apache-airflow-backport-providers-mysql for Apache Airflow

apache-airflow-backport-providers-neo4j — Backport provider package apache-airflow-backport-providers-neo4j for Apache Airflow

apache-airflow-backport-providers-odbc — Backport provider package apache-airflow-backport-providers-odbc for Apache Airflow

apache-airflow-backport-providers-openfaas — Backport provider package apache-airflow-backport-providers-openfaas for Apache Airflow

apache-airflow-backport-providers-opsgenie — Backport provider package apache-airflow-backport-providers-opsgenie for Apache Airflow

apache-airflow-backport-providers-oracle — Backport provider package apache-airflow-backport-providers-oracle for Apache Airflow

apache-airflow-backport-providers-pagerduty — Backport provider package apache-airflow-backport-providers-pagerduty for Apache Airflow

apache-airflow-backport-providers-papermill — Backport provider package apache-airflow-backport-providers-papermill for Apache Airflow

apache-airflow-backport-providers-plexus — Backport provider package apache-airflow-backport-providers-plexus for Apache Airflow

apache-airflow-backport-providers-postgres — Backport provider package apache-airflow-backport-providers-postgres for Apache Airflow

apache-airflow-backport-providers-presto — Backport provider package apache-airflow-backport-providers-presto for Apache Airflow

apache-airflow-backport-providers-qubole — Backport provider package apache-airflow-backport-providers-qubole for Apache Airflow

apache-airflow-backport-providers-redis — Backport provider package apache-airflow-backport-providers-redis for Apache Airflow

apache-airflow-backport-providers-salesforce — Backport provider package apache-airflow-backport-providers-salesforce for Apache Airflow

apache-airflow-backport-providers-samba — Backport provider package apache-airflow-backport-providers-samba for Apache Airflow

apache-airflow-backport-providers-segment — Backport provider package apache-airflow-backport-providers-segment for Apache Airflow

apache-airflow-backport-providers-sendgrid — Backport provider package apache-airflow-backport-providers-sendgrid for Apache Airflow

apache-airflow-backport-providers-sftp — Backport provider package apache-airflow-backport-providers-sftp for Apache Airflow

apache-airflow-backport-providers-singularity — Backport provider package apache-airflow-backport-providers-singularity for Apache Airflow

apache-airflow-backport-providers-slack — Backport provider package apache-airflow-backport-providers-slack for Apache Airflow

apache-airflow-backport-providers-snowflake — Backport provider package apache-airflow-backport-providers-snowflake for Apache Airflow

0 notes

alvarad982stedk · 6 years ago

Text

WHAT ARE COMMON PLASTIC PARTS FOR AUTOMOBILES?

Common automotive plastic parts are: dashboard body skeleton, battery bracket, front-end module, control box, seat support frame, spare placenta, fender, chassis cover, noise partition, rear door frame, etc. Most of the panels of automobile plastic parts are made of engineering plastic ABS or abs/pc.

Generally, doors, dashboards, bumpers and gearboards are all made of PP. Engine hood is made of lead with pp. PC / ABS is usually purchased from material manufacturers. Plastic parts are light in weight, and have a variety of colors, beautiful, good weight loss effect, but also can reduce the weight of the car body itself. It can be recycled and recycled many times.

In automobile recycling, metal products and other reasons are mostly too old and rusty to have recycling value. Because plastic products can be melted and regenerated, they can be processed twice after melting, and there will be no harm, so automotive plastic parts are more and more popular.

JasonMould Industrial Company Limited, established in 2010, is a leading China mold factory. JasonMould specializes in plastic mould production for household appliances, medical equipments, electronic equipments, safety equipments as well as monitoring system.

The company has over 15000 square metres factory. With plastic injection tooling divisions possessing different machinery and expertise, JasonMould offers tools from small and precise mobile phone parts to as big as automotive parts. Our tools are mainly exported to U.S.A., Europe, Japan and UK. JasonMould’s diversification strategy and full service has won compliment from customers all over the world.

Our mission is to provide our customers high quality moulding products and services. We aim to exceed our customers’ expectations of pricing, quality and on-time delivery. To achieve our mission, JasonMould:

Commits to continually improve employee skills and efficiency,

Provides our employees a clean and safe working environment,

Upgrades machine technology and support equipment through a strict maintenance program, and

Maintains customers’ tooling to its highest peak of performance

For more about China injection molding cost,please visit https://www.jasonmolding.com/

Inquiry Contact:

Contact person: James Yuan

Company name: JasonMould Industrial Company Limited

Address: LongGang Village,LongXi Town,BoLuo County,HuiZhou City,GuangDong Province, China

Telephone: 86-752-6682869

Email: [email protected]

Website: https://www.jasonmolding.com

0 notes

terabitweb · 6 years ago

Text

Original Post from Security Affairs Author: Pierluigi Paganini

Experts at Trend Micro discovered a new variant of the Asruex Trojan that exploits old Microsoft Office and Adobe vulnerabilities to infect systems.

Malware researchers at Trend Micro discovered a new variant of the Asruex Trojan that exploits old Microsoft Office and Adobe vulnerabilities to infect Windows and Mac systems.

Asruex first appeared in the threat landscape 2015, researchers linked it to the spyware used by the DarkHotelAPT group.

“However, when we encountered Asruex in a PDF file, we found that a variant of the malware can also act as an infector particularly through the use of old vulnerabilities CVE-2012-0158 and CVE-2010-2883, which inject code in Word and PDF files respectively.” reads the report published by Trend Micro.

CVE-2012-0158 is a critical remote code execution (RCE) vulnerability that affected Microsoft Office.

CVE-2010-2883 is a stack buffer overflow flaw that could be exploited by attackers to execute arbitrary code or trigger a denial of service condition.

The attack chain leverages a shortcut file that has a PowerShell download script, and spreads through removable drives and network drives.

The use of exploits for well-known vulnerabilities that have been already patched suggests that attackers aims at infect specific targets who have been using older versions of Adobe Reader (versions 9.x up to before 9.4) and Acrobat (versions 8.x up to before 8.2.5) on Windows and Mac OS X.

Because of this unique infection capability, security researchers might not consider checking files for an Asruex infection and continue to watch out for its backdoor abilities exclusively. Awareness of this new infection method could help users defend against the malware variant.

Trend Micro researchers discovered the new Asruex variant in malicious .PDF files that was spread via phishing messages.

Researchers reported that attackers also used weaponized Word files to deliver the Asruex Trojan, in other cases the malicious code is delivered as a standard executable.

“This Asruex variant compresses and encrypts the original executable file or host file and appends it as its .EBSS section. This allows the malware to drop the infector, while also executing the host file like normal.” continues the report.

Once executed on a machine, Asruex will check the following information to determine if it is running in a sandbox environment:

Computer names and user names

Exported functions by loaded modules

File names

Running processes

Module version of running process

Certain strings in disk names

If the systems passes the checks, the backdoor is installed on the system.

“This case is notable for its use of vulnerabilities that have been discovered (and patched) over five years ago, when we’ve been seeing this malware variant in the wild for only a year,” Trend Micro concludes. “This hints that the cybercriminals behind it had devised the variant knowing that users have not yet patched or updated to newer versions of the Adobe Acrobat and Adobe Reader software.”

window._mNHandle = window._mNHandle || {}; window._mNHandle.queue = window._mNHandle.queue || []; medianet_versionId = "3121199";

try { window._mNHandle.queue.push(function () { window._mNDetails.loadTag("762221962", "300x250", "762221962"); }); } catch (error) {}

Pierluigi Paganini

(SecurityAffairs – Asruex Trojan, malware)

The post A new variant of Asruex Trojan exploits very old Office, Adobe flaws appeared first on Security Affairs.

#gallery-0-6 { margin: auto; } #gallery-0-6 .gallery-item { float: left; margin-top: 10px; text-align: center; width: 33%; } #gallery-0-6 img { border: 2px solid #cfcfcf; } #gallery-0-6 .gallery-caption { margin-left: 0; } /* see gallery_shortcode() in wp-includes/media.php */

Go to Source Author: Pierluigi Paganini A new variant of Asruex Trojan exploits very old Office, Adobe flaws Original Post from Security Affairs Author: Pierluigi Paganini Experts at Trend Micro discovered a new variant of the Asruex Trojan that exploits old Microsoft Office and Adobe vulnerabilities to infect systems.

#Security Affairs blog

0 notes

mbaljeetsingh · 6 years ago

Text

Getting Started with Nest.js

If you have ever worked on a Node.js application before, either built a REST API or an enterprise application, you must have realised how tedious and daunting it was to maintain, especially whenever the application start to scale. The more you add new features to the application, the larger the codebase.

Creating a proper structure for such application can result into serious headache if not properly managed, especially as a result of application specific configurations. This is why Nest.js was created.

Nest.js was built mainly to eliminate disorganized codebases and give Node.js application a moderate and reasonable structure out of the box. Heavily inspired by Angular, Nest.js was built with TypeScript and uses Express.js under hood. This rightly makes it compatible with the majority of express middleware.

In this post, I will introduce and take you through the process of getting started with Nest.js. You will learn about several ways to install the framework on your machine and why you need to consider using it for your next project. In the process of doing this, you will create a very simple RESTful API that enables users to fetch, create and delete books in a bookstore.

This is a very simple application but yet broad enough to give you comprehensive insight on how to craft an application with Nest.js.

Familiarity with TypeScript and a reasonable knowledge of JavaScript will help you get the best out of this tutorial. Experienced with building applications with Angular will be a plus but not a requirement as the article will give you a proper guide on how to easily begin.

You need to install Node and npm. It is advisable to also install nodemon globally on your machine.

Nest.js is a server-side Node.js framework for building efficient, reliable and scalable applications. Built by Kamil and backed by quite a number of reputable organizations and individuals.

Nest.js was introduced to solve the architectural problem of Node.js by giving backend applications a modular structure for organising code into separate modules.

Fully built with TypeScript, it comes with the benefits of code type checking and dependency injection which helps to facilitate the process of development of applications. If you are conversant with the structure of Angular applications, you are going to feel so comfortable with the key concepts of Nest.js and getting started with it will be quite an easy task. Anyways, this post will provide you with the required details needed to start building applications with Nest.js.

In addition, the following list shows some of the benefits of Nest.js as explained here by Kamil:

it surrounds your route handler body with try..catch blocks

it makes every route handler async

it creates a global express router

Free Node eBook

Build your first Node apps and learn server-side JavaScript.

Thank you!

You have successfully joined the Scotchy super duper web dev awesome mailing list.

it creates a separated router for each controller

it binds error-handling middleware

it binds body-parser middleware (both json and extended urlencoded)

Now that you have been briefed about this awesome framework, let’s take a look at the building blocks of Nest.js.

The following are the building blocks used when building Nest.js applications:

Controllers

Typical to most web frameworks, controllers in Nest.js are responsible for handling any incoming requests and returning responses to the client side of the application. For example, if you make an API call to a particular endpoint, say /home, the controller will receive this request and based on the available resources, it will returned the appropriate response.

Nest.js was structured in a way that the routing mechanism is able to control which controller will be responsible for handling a particular request.

Defining a basic controller in Nest.js is as good as creating a TypeScript file and including a decorator @Controller() just like the code snippet below:

// users.controller.ts import { Controller, Get } from '@nestjs/common'; @Controller('users') export class UsersController { @Get() findAll() { return 'This will return all the users'; } }

The prefix of users within the Controller decorator will prompt the UsersController to handle any /users GET request within an application and return the appropriate response as specified. Other HTTP request handled by the controller includes POST , PUT, DELETE as we will see later in the tutorial.

Once a controller is created, it needs to be added to the module definition before Nest.js can easily recognise it. This could be the root ApplicationModule or any other module created within the application. More about this in the module section of this post.

As mentioned earlier, Nest.js was heavily inspired by Angular and similar to an Angular application, one can easily create a provider and inject it into controllers or other providers too as well. These providers are also called services and based on the philosophy of Nest.js, it was designed to abstract any form of complexity and logic to a class called service.

A service provider in Nest.js is just a normal JavaScript class with a special @Injectable() decorator at the top.

For example, you can simply create a service to fetch users as shown below:

// users.service.ts import { Injectable } from '@nestjs/common'; import { User } from './interfaces/user.interface'; @Injectable() export class UsersService { private readonly users: User[] = []; create(user: User) { this.users.push(user); } findAll(): User[] { return this.users; } }

The provider created above is a class with two methods create() and findAll(), which can be used to create and return all users respectively. And to easily help with type checking an interface was used to specify the type of elements that should be received by the methods.

Modules are more like the most important basic building block in Nest.js. They are TypeScript files decorated with @Module decorator. This attached decorator provides metadata that Nest makes use of to organize the application structure. With modules you can easily group related files into one.

Each Nest.js application must have at least one module, usually referred to as the root module. This root module is the top-level module and usually enough for a small application but it is advisable to break a large application into multiple modules as it helps to maintain the structure of the application.

If you have an application that manages a lot of data or functionality about users , we can group both the controller, services and other related files into a single module, say UsersModule for example:

import { Module } from '@nestjs/common'; import { UsersController } from './users.controller.ts'; import { UsersService } from './users.service.ts'; @Module({ controllers: [UsersController], providers: [UsersService] }) export class UsersModule {}

From the preceding file, we are exported a UsersModule that contains both the UsersController and UsersService. With this in place, we can then proceed to import and use the UsersModule within the root module of the application as shown in the following code snippet:

... import { UsersModule } from './users/users.module'; @Module({ ... }) export class AppModule { }

DTO

Data transfer object is an object that defines how data will be sent over the network.

Interfaces

TypeScript interfaces are used for type-checking and defining the types of data that can be passed to a controller or a Nest service.

Dependency injection

Dependency injection is a design pattern used to increase efficiency and modularity of applications. It is often used by the biggest frameworks to keep code clean and easier to use. Nest.js also makes use of it to basically create coupled components.

With this pattern, it is very easy to manage dependencies between building blocks like controllers, providers and modules. The only thing required is to define the dependency for example a UsersService() in the constructor of a controller as shown here:

... @Controller('users') export class UsersController { constructor(private readonly usersService: UsersService){} ... }

With some of these concepts briefly covered, you can now proceed to the next section, where you will put all the knowledge gained so far in this post into use as you will learn how to seamlessly build a RESTful API using Nest.js.

As stated earlier in this post, you will create a sample application that will help you get a good grasp on some of the core concepts of Nest.js.

This application will be specifically for a bookstore. At the end of the post you would have created a micro-service that will enable users to create and add a new book with few descriptions to an existing list of books. This could be from a database, but to ensure simplicity in this post, we won’t really be connecting our application to a database yet. But instead, we will make use of a mock data of books and once a new book is created, we will push and add it to the list.

In order to easily scaffold a new Nest.js application, you will need to globally installed Nest CLI. It is a command line interface tool specifically created to amongst other things, help to craft a new Nest.js app in no time and provide access to ( built in generators ) several commands to generate different files and produce a well-structured application.

Apart from using the CLI tool, you can also install a new Nest.js application by cloning the starter project from GitHub using Git, but for the purpose of this tutorial run the following command to install the Nest CLI:

npm i -g @nestjs/cli

This will give you access to the nest command for project installation and other project specific commands.

Next, run the command below to install a new project named bookstore-nest within your development folder:

nest new bookstore-nest

You will be asked few questions during the installation, just follow the prompt and respond accordingly. Next, once the installation is complete, change directory into the newly created project and start the application with:

// change directory cd bookstore-nest // start the application npm run start

or better still, run the command below in order to use Nodemon for the project:

// start the application using nodemon npm run start:dev

Navigate to http://localhost:3000 from your favorite browser, you will see the Hello World! message as shown here:

First you will start by generating a module for the bookstore. To do this, you will leverage the inbuilt file generator using Nest CLI. Run the following command to scaffold a new module for the application:

nest generate module books

The command above will create a new folder named books within the src folder. Also within the books folder you will find a books.module.ts file.

// ./src/books/books/module.ts import { Module } from '@nestjs/common'; @Module({}) export class BooksModule {}

This was generated by the command and the module has also been added to the app.module.ts which happens to be the root module of the application.

Next, you will create routes for the endpoints. As mentioned earlier, routes are in controllers, so you need to create controllers that will handle individual endpoints. Again, use Nest CLI to generate your controllers, run the following command:

nest generate controller books

This will create a controller inside the books folder. Since we won’t really be connecting to the database for now, create a sample mock data for the bookstore. Under the src folder, create a subfolder named mocks and within the newly created folder, create a new TypeScript file named books.mock.ts and paste the following code in it:

// ./src/mocks/books.mock.ts export const BOOKS = [ { id: 1, title: 'First book', description: "This is the description for the first book", author: 'Olususi Oluyemi' }, { id: 2, title: 'Second book', description: "This is the description for the second book", author: 'John Barry' }, { id: 3, title: 'Third book', description: "This is the description for the third book", author: 'Clement Wilfred' }, { id: 4, title: 'Fourth book', description: "This is the description for the fourth book", author: 'Christian nwamba' }, { id: 5, title: 'Fifth book', description: "This is the description for the fifth book", author: 'Chris anderson' }, { id: 6, title: 'Sixth book', description: "This is the description for the sixth book", author: 'Olususi Oluyemi' }, ];

Next, you will create a service to hold all the logic for the bookstore. Run the following command to generate a service:

nest generate service books

This command will create a new file named books.service.ts within ./src/books folder.

Next, open the newly created file and paste the following:

// ./src/books/books.service.ts import { Injectable, HttpException } from '@nestjs/common'; import { BOOKS } from '../mocks/books.mock'; @Injectable() export class BooksService { books = BOOKS; getBooks(): Promise<any> { return new Promise(resolve => { resolve(this.books); }); } getBook(bookID): Promise<any> { let id = Number(bookID); return new Promise(resolve => { const book = this.books.find(book => book.id === id); if (!book) { throw new HttpException('Book does not exist!', 404); } resolve(book); }); } }

First, you imported the requires modules from Nest.js and also BOOKS from the mock data you created earlier.

Next, you created two different methods named getBooks() and getBook() to retrieve the list of books from the mock data and to fetch just one book using the bookID as a parameter.

Next, add the method below to the /src/books/books.service.ts immediately after the getBook() method:

The method above will be used to push a new book to the existing list

Finally, add the last method to delete a particular book using the bookID as a parameter:

// ./src/books/books.service.ts import { Injectable, HttpException } from '@nestjs/common'; import { BOOKS } from '../mocks/books.mock'; @Injectable() export class BooksService { books = BOOKS; ... deleteBook(bookID): Promise<any> { let id = Number(bookID); return new Promise(resolve => { let index = this.books.findIndex(book => book.id === id); if (index === -1) { throw new HttpException('Book does not exist!', 404); } this.books.splice(1, index); resolve(this.books); }); } }

Here, you will use dependency injection design pattern to pass the BooksService into the BooksController through a constructor. Open the BooksController created earlier and paste the following code in it:

// ./src/books/books.controller.ts import { Controller, Get, Param, Post, Body, Query, Delete } from '@nestjs/common'; import { BooksService } from './books.service'; import { CreateBookDTO } from './dto/create-book.dto'; @Controller('books') export class BooksController { constructor(private booksService: BooksService) { } @Get() async getBooks() { const books = await this.booksService.getBooks(); return books; } @Get(':bookID') async getBook(@Param('bookID') bookID) { const book = await this.booksService.getBook(bookID); return book; } @Post() async addBook(@Body() createBookDTO: CreateBookDTO) { const book = await this.booksService.addBook(createBookDTO); return book; } @Delete() async deleteBook(@Query() query) { const books = await this.booksService.deleteBook(query.bookID); return books; } }

Here in this controller, first, the important modules were imported from @nestjs/common and you also import both the BooksService and CreateBookDTO respectively. CreateBookDTO is a data transfer object, a TypeScript class created for type-checking and to define the structures of what an object looks like when creating a new book. We will create this DTO in a bit.

Next, you used constructor to inject the BooksService into the controller and created four different methods which are:

getBooks(): Used to fetch the list of all books. It has @Get() decorator attached to it. This helps to map any GET request sent to /books to this controller.

getBook(): Used to retrieve the details of a particular book by passing the bookID as a parameter.

addBook(): Used to create and post a new book to the existing book list. And because we are not persisting into the database, the newly added book will only be held in memory.

deleteBook(): Used to delete a book by passing the bookID as a query parameter.

Each of the methods has a special decorator attached to it, which makes it very easy to route each HTTP request to a specific method within the controller.

In the previous section, you made use of a data transfer object called CreateBookDTO. To set it up, navigate to the ./src/books folder and create a new subfolder name dto. Next, within the newly created folder, create another file and call it create-book.dto.ts and paste the following in it:

// ./src/books/dto/create-book.dto.ts export class CreateBookDTO { readonly id: number; readonly title: string; readonly description: string; readonly author: string; }

You are almost done with the application, the next line of action is to take a look at the BooksModule and update it accordingly. You will do that in the next section.

Navigate back to the BooksModule created earlier and update it with the code below:

// ./src/books/books.module.ts import { Module } from '@nestjs/common'; import { BooksController } from './books.controller'; import { BooksService } from './books.service'; @Module({ controllers: [BooksController], providers: [BooksService] }) export class BooksModule {}

Start the application again if it is not running at the moment with:

npm run start

and use postman to test the API

We have barely scratched the surface on what Nest.js has to offer the Node.js world in this post. To get more conversant with this awesome framework, first, we took a quick look at the fundamentals and basic building blocks of Nest.js and then proceeded to build a RESTful API where you also learnt about dependency injection amongst other things.

I hope this tutorial as given you enough information to try out Nest.js for your next application. Feel free to drop your thoughts in the comment section below and find the complete source code of this tutorial here on GitHub.

via Scotch.io http://bit.ly/2R5NVbh

#IFTTT #Feedly

0 notes

worldwidereports-blog · 7 years ago

Text

Medical Micro Injection Molding Market - Size, Share, Outlook, and Forecast till 2026

Worldwide Market Reports added Latest Research Report titled “Medical Micro Injection Molding Market ”to its Large Report database.

Micro injection molding is a method by which parts and tools are molded into miniature modules using machines with high pressure. Micro injection molding finds applications in sensors, optics, micromechanics, telecommunication, micro drove systems and control, watches, automotive components, electronics, and medical. In the medical industry, it is used in the manufacturing of parts such as sensors, implants, tubes, catheter tips, micro optics, and others. Key markets for medical micro molding include orthopedic, drug delivery, cardiovascular, drug delivery, neurological, and closure.

The global medical micro injection molding market is expected to witness significant growth over the forecast period, owing to the replacement of machined components with molded products. Rising trend of small devices and increasing number of minimally invasive surgeries have led to an increasing demand for micro sized parts from medical device manufacturers, which will drive growth of the medical micro injection molding market.

Moreover, the rapid development of micro fluidics technology is also expected to boost growth of the medical micro injection molding market over the forecast period. High cost savings due to use of low cost raw materials and less time taken for the process of molding are also expected to increase the demand for micro injection molding in medical industry, thereby fueling growth of the market.

However, lack of awareness about micro molding and its high costs in the emerging economies are expected to hamper growth of the global medical micro injection molding market.

Request for Sample Copy of Research Report: https://www.worldwidemarketreports.com/sample/197668

Key Developments in Medical Micro Injection Molding Market

Key players are adopting various strategies such as mergers, acquisitions, new product launches, expansions, collaborations, partnerships, approvals, and joint ventures to retain its position in the medical micro injection molding market. On October 14, 2016, MTD Micro Molding, a long-time leader in micro-injection molding for the medical device industry, was announced as the first micro molding company in the world to achieve MedAccred Certification.

On February 27, 2017, Kohlberg & Company, L.L.C., a leading private equity firm specializing in middle-market investing, announced the acquisition of Pexco LLC, a leading North American specialty plastics manufacturer, from Odyssey Investment Partners, LLC.

Some of the major players operating in the global medical micro injection molding market include SMC, BMP Medical, Stamm AG, MicroPEP, MTD Micro Molding, PEXCO, Sovrin Plastics, Accumold, Microsystems, Mikrotech, Kamek Precision Tools, Makuta Technics, Stack Plastics, Precimold, American, Precision Products, and Rapidwerks

Get Best Discount on Research Report: https://www.worldwidemarketreports.com/discount/197668

Report includes chapters which deeply display the following deliverable about industry: • Medical Micro Injection Molding Market Research Objective and Assumption • Medical Micro Injection Molding Market Purview - Report Description, Executive Summary, and Coherent Opportunity Map (COM) • Medical Micro Injection Molding Market Dynamics, Regulations, and Trends Analysis - Market Dynamics, Regulatory Scenario, Industry Trend, Merger and Acquisitions, New system Launch/Approvals, Value Chain Analysis, Porter’s Analysis, and PEST Analysis • Global Medical Micro Injection Molding Market, By Regions • Medical Micro Injection Molding Market Competition by Manufacturers including Production, Share, Revenue, Average Price, Manufacturing Base Distribution, Sales Area and Product Type. • Medical Micro Injection Molding Market Manufacturers Profiles/Analysis including Company Basic Information, Manufacturing Base and Its Competitors. • Medical Micro Injection Molding Market Manufacturing Cost Analysis including Key Raw Materials and Key Suppliers of Raw Materials. • Industrial Chain, Sourcing Strategy and Downstream Buyers including Upstream Raw Materials Sourcing and Downstream Buyers • Marketing Strategy Analysis, Distributors/Traders including Marketing Channel, Market Positioning and Distributors/Traders List. • Market Effect Factors Analysis including Technology Progress/Risk, Consumer Needs/Customer Preference Change and Economic/Political Environmental Change. • Medical Micro Injection Molding Market Forecast including Production, Consumption, Import and Export Forecast by Type, Applications and Region. • Research Findings and Conclusion.

**If you have any special requirements, please let us know and we will offer you the report as you want.

About WMR

Worldwide Market Reports is your one-stop repository of detailed and in-depth market research reports compiled by an extensive list of publishers from across the globe. We offer reports across virtually all domains and an exhaustive list of sub-domains under the sun. The in-depth market analysis by some of the most vastly experienced analysts provide our diverse range of clients from across all industries with vital decision making insights to plan and align their market strategies in line with current market trends. Worldwide Market Research’s well-researched inputs that encompass domains ranging from IT to healthcare enable our prized clients to capitalize upon key growth opportunities and shield against credible threats prevalent in the market in the current scenario and those expected in the near future.

Mr. Shah

Worldwide Market Reports

1001 4th Ave,

#3200

Seattle, WA 98154,

U.S

Tel: +1 415 871 0703

Email: [email protected]

#Medical Micro Injection Molding Market #Medical Micro Injection Molding #Medical Micro Injection Molding Industry #Medical Micro Injection Molding share

0 notes

t-baba · 7 years ago

Photo

Using Angular Augury to Debug Your Code

Augury is an open-source tool allowing developers to profile and debug Angular 2 and 4 applications.

Modern web browsers provide developer consoles to inspect various elements on the page, which is really handy when trying to debug markup, styles, and scripts. However, this console isn’t enough to debug Angular applications that usually have lots of components, events, attributes, and a separate routing system.

Augury is a tool designed specifically for Angular apps. It’s an open-source debugging and profiling tool for Angular 2+ applications.

Augury is just a Chrome extension that’s quite simple to use, so you won’t need to spend hours and hours learning how to utilize this tool. We’re going to build a sample Angular app and then see Augury in action by exploring various parts of our project. So, let’s get started!

Hello, Augury!

Augury visualizes your app’s structure in a form of a tree, showing how components and their dependencies relate to each other. It also allows you to inspect properties of your objects and change them on the fly. On top of that, you can easily view the source code of a specific component, insert breakpoints as needed, work with events, and more. Lastly, you can browse the application’s routing system, as well as view the full list of all utilized modules.

Augury is only available as a Chrome extension (there’s no Firefox support yet, unfortunately) and installing it is as simple as going to this page and pressing the Install button. After that, you may open the developer tools by pressing Ctrl + Shift + I (Windows/Linux) or Cmd + Opt + I (macOS). You’ll note that a new tab called Augury has appeared. After switching to this tab, you’ll either see the application’s structure or the phrase “This application is not an Angular application”. I’ve noticed that sometimes it may be required to re-open the Developer Console in order for Augury to analyze the page properly, so watch out.

Now that we have Augury installed, let’s proceed to the next section and prepare the sample application that we’ll use as a playground!

Building a Sample App

In order to see Augury in action, we need something to debug, right? In this section, I’m going to quickly guide you through the process of creating a very simple application (loosely based on the sample app from the Angular’s official tutorial) listing some users and allowing you to edit them. Alternatively, you may grab the source code from my GitHub repo.

Before getting started, install Angular CLI on your machine if you don’t have it yet:

npm install -g @angular/cli

Next, create the skeleton of our new project:

ng new sitepoint-augury

Change the application’s title by tweaking the src/app/app.component.ts file:

// ... export class AppComponent { title = 'Augury Demo'; }

Tweak the src/app/app.component.html by removing all the links to documentation added automatically by code generator and add an <app-users></app-users> line:

<div style="text-align:center"> <h1> Welcome to ! </h1> </div> <app-users></app-users>

Of course, we need a User component, so generate it now by running:

ng generate component users

Change the src/app/users/user.component.ts file in the following way:

import { Component, OnInit } from '@angular/core'; import { User } from './user.model'; // <--- 1 import { UserService } from './user.service'; // <--- 2 @Component({ selector: 'app-users', templateUrl: './users.component.html', styleUrls: ['./users.component.css'] }) export class UsersComponent implements OnInit { users: User[]; selectedUser: User; onSelect(user: User): void { // <--- 3 this.selectedUser = user; } constructor(private userService: UserService) { } // <--- 4 ngOnInit() { this.getUsers(); // <--- 5 } getUsers(): void { // <--- 6 this.users = this.userService.getUsers(); } }

Main things to note here:

We are importing a User model that will be created in a moment.

We’re also importing a UserService. It will simply return a list of hardcoded users, but let’s pretend they’re being fetched from some remote location.

We’re allowing the users to be selected by clicking on them. The currently selected user is stored in a separate selectedUser attribute.

Hook up the userService using the dependency injection mechanism.

Load the list of users once the component is initialized.

In order to get users, we’re utilizing our userService.

That’s pretty much it for this component.

Next, let’s create a model in a src/app/users/user.model.ts file. Each user is going to have an ID, a first and a last name:

export class User { id: number; first: string; last: string; }

Nothing complex.

Now let’s proceed to the UserService that’s going to be defined in the app/src/users/user.service.ts file:

import { Injectable } from '@angular/core'; import { User } from './user.model'; @Injectable() export class UserService { constructor() { } getUsers(): User[] { return [ { id: 1, first: 'John', last: 'Doe' }, { id: 2, first: 'Margaret', last: 'Brown' } ] } }

The getUsers method simply returns an array of users with hardcoded data.

Now let’s display our users with the help of ngFor. Also, we’re going to add a click event listener and fire onSelect whenever a user is clicked on. When this happens, a form to edit the chosen user should be displayed (which is going to be done with the help of ngIf). Modify the src/app/users/user.component.html file like this:

<div *ngFor="let user of users" (click)="onSelect(user)" [class.selected]="user === selectedUser"> <p>, (ID: )</p> </div> <div *ngIf="selectedUser"> <h3>Edit</h3> <label for="first">First</label> <input [(ngModel)]="selectedUser.first" placeholder="First name" id="first"> <label for="last">Last</label> <input [(ngModel)]="selectedUser.last" placeholder="Last name" id="last"> </div>

We’re assigning a .selected CSS class to the chosen user, so let’s add some simple styling for it inside the src/app/users/user.component.css file:

.selected { font-weight: bold; }

Lastly, we have to import FormsModule and UserService inside the src/app/app.module.ts file:

import { BrowserModule } from '@angular/platform-browser'; import { NgModule } from '@angular/core'; import { FormsModule } from '@angular/forms'; // <--- import { UserService } from './users/user.service'; // <--- import { AppComponent } from './app.component'; import { UsersComponent } from './users/users.component';

FormsModule should be listed in the imports section in the app.module.ts, whereas UserService goes to the providers:

@NgModule({ declarations: [ AppComponent, UsersComponent ], imports: [ BrowserModule, FormsModule // <--- ], providers: [ UserService // <--- ], bootstrap: [AppComponent] })

That’s it! Our sample application is finished, and you can open it by running the following command:

ng serve --open

Continue reading %Using Angular Augury to Debug Your Code%

by Ilya Bodrov-Krukowski via SitePoint https://ift.tt/2xjBGTw

#CSS3 #HTML5 Branding #HTML5 Weekly #HTMLl5 demos #Javascript Branding #Javascript Weekly #Mobile #Mo

0 notes

blueprintnewspapers-blog · 7 years ago

Text

Assessing Haruna‘s Change Mantra in NASENI

New Post has been published on http://blueprint.ng/assessing-harunas-change-mantra-in-naseni/

Assessing Haruna‘s Change Mantra in NASENI

By Best Agbese

Nigerians have held President Muhammadu Buhari on public accountability strictly on his professed sobriquet of “Change mantra,” in the administration of Nigeria. Before May 2015, there was a unanimous consensus among Nigerians that the country had slipped into very dangerous abyss of ennui, where virtually all public institutions and agencies collapsed pathetically, amid mounting problems. Therefore, President Buhari ascended the Presidency of Nigeria on the banner of a reformer and redeemer, with a vow to change the narrative positively. And frantically, all civilized nations assume the status through the development and promotion of science and technology. However, its application in Nigeria was not only abandoned, but regrettably disappeared from the binoculars and psyche of national planners or policy makers. President Buhari’s retention of the Ministry of Science and Technology, after trimming down the number of ministries sent his signals to pull back Nigeria from this regressive obscurity of Science and technology in national life. Hitherto, some federal agencies like the National Agency for Science and Engineering Infrastructure (NASENI) were cold- dead agencies, which existed only in nomenclature and a huge staff base. NASENI, with a gargantuan mandate ought to have been the bedrock of the development of science and technology, failed to register its presence in tackling the multifaceted challenges of a technology-driven economy of Nigeria. But the mindset and focus of Mr. President has rejigged the tale. And in NASENI specifically, an agency mandated to provide engineering infrastructure to effectively service the nation’s technological needs in consumables’, has attuned into the “change mantra” code. An archetypal, professional engineer cum administrator per excellence, Prof. Haruna, has dramatized his ingenuity in leadership of the agency, in consonance with President Buhari’s leadership of Nigeria. Buhari , who is the Executive Chairman and doubles as chairman, Governing Board of NASENI . The EVC/DG has placed the agency and its dozen institutes, perpetually on a fast rewarding lane of productivity as exposed in this interview that “NASENI has continued to design and fabricate products that have bettered the lives of Nigerians and also transferred these technologies to SMEs.” Like President Buhari, Professor Haruna unmistakably blends words with action and the vaults of NASENI under the few years of his leadership display admirable and fascinating treasures in indigenous technology. An ardent apostle of the Executive Order on Local content, the EVC has struck partnerships and synergies with local partners in enhancing the work of the agency. He has leveraged on the commonplace technological void, which afflict Nigerians, but attract huge foreign exchange expenditure to deliver his message of emancipation to Nigerians. The agency’s shadows now roam splendidly in power, industrial, education, agriculture, transport sectors as well as in mechanical re-engineering of the electronic voting system. It is to NASENI’s credit that some Nigerian communities now regale in micro-power generation liberty with the development of locally researched and produced Small hydropower (SHP) Propeller Turbines of three different models. The brainchild of the Engineering Materials Development Institute (EMDI), the Turbines are already effectively supplying 10 KW electricity to communities, like the Awara Dam facility in Ikare, Ondo state. To demonstrate his leadership prowess, NASENI under Haruna has crazily romanced technology in many novel ways. The Ikeji-ille Ijesa community in Osun state is powered by the agency’s Cross Flow Turbine , which generates up to 70 KW of electricity. And likewise, the Mada Community at Gudi hamlet, in Nasarawa state has continued to celebrate a 5 KW Kinetic Turbine installed for power supply. And further deconstructing the underbelly of hydro-power generation in Nigeria, NASENI has also developed a 10 KW Propeller Turbine, whose capacity to generate power is merely pressure from a pipe -borne water source. But with eyes set on long targets, Professor Haruna has reactivated and upgraded the 5 MW Solar panel manufacturing plant at Karshi, Abuja and converted into a limited liability company renamed as NASENI Solar Energy Limited (NSEL). At the moment, NSEL produces solar panels and modules for Nigerians. It has also developed a high voltage testing laboratory, a vital component or unit for all power generation companies. And by 2019, through a partnership with a firm in China, its capacity is planned to jerk up to 25MW and, an increased local content targeted to jump from 40- 95 percent, to land a mass production of cheaper solar panels and power transformers for domestic uses and exportation to other African nations. The agricultural sector, which is another prime sector President Buhari has targeted for attaining food security and self-sufficiency, in the bid to diversify Nigeria’s mono-economy, NASENI has registered imprints. Professor Haruna has actualized the development of efficient Deep Well hand pumps and centrifugal pumps for irrigation purposes in the pursuit of all-year farming agenda of Nigeria. Through the technique of reverse engineering, the agric sector is also infested with other goodies, as farmers can now boast of mobile cassava graters, rice threshers and harvesters, yam pounding machines, fish dryer, table top seed oil mills for easy extraction of oil from various genetic seeds. However, NASENI has pleasantly shocked Nigerians by pioneering the development of first made- in Nigeria passenger and cargo tricycles with improved features. These are low cost vehicles, and designed for the convenience of rural dwellers, intended to solve the haunting problems of haulage of agric produce from rural areas to urban market centers. It like, the EVC has a knack for scoring first. So, the Haruna led agency has also produced the first made- in Nigeria motorcycle, with 65 percent of its components locally sourced. And plans are in top gear to commence mass production anytime from now. Nigeria’s industrial sector is experiencing a blaze of glorious moments and products. NASENI has launched multiple mud brick making machines and Injection nozzles. it is producing machine components/spare parts and molds, which has sent a message to the outside world that the indigenous importation racket would soon be broken. Added, there is NASENI engineered Laterite Grinders as well as Laterite Mixers, whose proficiency is comparable to foreign ones and a lot similar interventions in the offing. And in order to vacate the perennial problem of electoral malfeasances prevalent in Nigeria and Africa generally, through credible polls, a unique solar-powered electronic voting machine (e-voting machine) has been developed. It has cloud-based collation of election results devices anywhere. Some, other outstanding features of the e-voting machine ensures and guarantees all segments of elections on the same day and time, much as conveying electronically, flawless or indisputable results. These days, national agencies and institutions like the Nigeria Airforce (NAF) have found NASENI convenient a destination for personnel and technicians training in networking tools and techniques in line with the Executive Order on local content for goods and services. This was impossible in the past, as foreign trainings would have usurped such roles for lack of a suitable, viable and functional internal agency like NASENI to render such services. It is therefore, pertinent to buttress that Professor Haruna’s leadership of NASENI is configured after President Buhari’s mindset and actions in tandem with the “change mantra.” To understand that despite the poor funding of the agency, he has been able to promenade the agency on the path of unprecedented development is commendable. Nigeria is craving for the sort of quality and focused leadership offered by Professor Haruna as the helmsman of NASENI. Its quite amazing that the results as manifest in work done is far beyond the limits of federal resources at its disposal. It again, trumpets Buhari’s message of inward search for solutions to Nigeria’s problems by the different heads in the lower rungs of leadership. No wonder, this devout and result-oriented leader, has earned the confidence of the Honorable Minister of Science and Technology, Dr. Ogbonnaya Onu, another scientific guru. He has entrusted Professor Haruna with chairmanship of various committees in the ministry to illuminate the path of development in science and technology for Nigeria.

Agbese holds a Master of Science in Oil and Gas Engineering from Coventry University, United Kingdom

#agencies #dangerous

0 notes