git

Should you care about digital waste?

Watch my video and see why it’s so important to minimize digital waste. Are you aware of how much digital waste your WordPress website is producing? Did you know this waste carries an actual cost for both you and your website’s visitors? Digital waste is an especially poignant topic in open source software (like the […]





git

Global Gitignore Files Are Cool and So Are You

Setting it up

First, here's the config setup you need to even allow for such a radical concept.

  1. Define the global gitignore file as a global Git configuration:

    git config --global core.excludesfile ~/.gitignore
    

    If you're on OSX, this command will add the following config lines in your ~/.gitconfig file.

    [core]
      excludesfile = /Users/triplegirldad/.gitignore
    
  2. Load that ~/.gitignore file up with whatever you want. It probably doesn't exist as a file yet so you might have to create it first.

Harnessing its incredible power

There are only two lines in my global gitignore file and they are both fairly useful pretty much all the time.

$ cat ~/.gitignore
TODO.md
playground

This 2 line file means that no matter where I am, what project I'm working on, where in the project I'm doing so, I have an easy space to stash notes, thoughts, in progress ideas, spikes, etc.

TODO.md

More often than not, I'm fiddling around with a TODO.md file. Something about writing markdown in your familiar text editor speaks to my soul. It's quick, it's easy, you have all the text editing tricks available to you, and it never does anything you wouldn't expect (looking at you auto-markdown-formatting editors). I use one or two # for headings, I use nested lists, and I ask for nothing more. Nothing more than more TODO.md files that is!

In practice I tend to just have one TODO.md file per project, right at the top, ready to pull up in a few keystrokes. Which I do often. I pull this doc up if:

  • I'm in a meeting and I just said "oh yeah that's a small thing, I'll knock it out this afternoon".
  • I'm halfway through some feature development and realize I want to make a sweeping refactor elsewhere. Toss some thoughts in the doc, and then get back to the task at hand.
  • It's the end of the day and I have to switch my brain into "feed small children" mode, thus obliterating everything work-related from my short term memory. When I open things up the next day and know exactly what the next thing to dive into was.
  • I'm preparing for a big enough refactor and I can't hold it all in my brain at once. What I'd give to have an interactive 3D playground for brain thoughts, but in the meantime a 2D text file isn't a terrible way to plan out dev work.

playground

Sometimes you need more than some human words in a markdown file to move an idea along. This is where my playground directory comes in. I can load this directory up with code that's related to a given project and keep it out of the git history. Because who doesn't like a place to play around.

I find that this directory is more useful for long running maintenance projects over fast moving greenfield ones. On the maintenance projects, I tend to find myself assembling a pile of scripts and experiments for various situations:

  • The client requests a one-time obscure data export. Whip up some CSV generation code and save that code in the playground directory.
  • The client requests a different obscure data export. Pull up the last time you did something vaguely similar and save yourself the startup time.
  • A batch of data needs to be imported just once. Might as well stash that in the chance that "just once" is actually "just a few times".
  • Kicking the tires on an integration with a third party service.

Some of these playground files end up being useful more times than I can count (eg: the ever-changing user_export.rb script). Some items get promoted into application code, which is always fun. But most files here serve their purpose and then wither away. And that's fine. It's a playground, anything goes.

Wrapping up

Having a personal space for project-specific notes and code has been helpful to me over the years as a developer on multiple projects. If you have your own organizational trick, or just want to brag about how you memorize everything without any markdown files, let me know in the comments below!




git

Global Gitignore Files Are Cool and So Are You

Setting it up

First, here's the config setup you need to even allow for such a radical concept.

  1. Define the global gitignore file as a global Git configuration:

    git config --global core.excludesfile ~/.gitignore
    

    If you're on OSX, this command will add the following config lines in your ~/.gitconfig file.

    [core]
      excludesfile = /Users/triplegirldad/.gitignore
    
  2. Load that ~/.gitignore file up with whatever you want. It probably doesn't exist as a file yet so you might have to create it first.

Harnessing its incredible power

There are only two lines in my global gitignore file and they are both fairly useful pretty much all the time.

$ cat ~/.gitignore
TODO.md
playground

This 2 line file means that no matter where I am, what project I'm working on, where in the project I'm doing so, I have an easy space to stash notes, thoughts, in progress ideas, spikes, etc.

TODO.md

More often than not, I'm fiddling around with a TODO.md file. Something about writing markdown in your familiar text editor speaks to my soul. It's quick, it's easy, you have all the text editing tricks available to you, and it never does anything you wouldn't expect (looking at you auto-markdown-formatting editors). I use one or two # for headings, I use nested lists, and I ask for nothing more. Nothing more than more TODO.md files that is!

In practice I tend to just have one TODO.md file per project, right at the top, ready to pull up in a few keystrokes. Which I do often. I pull this doc up if:

  • I'm in a meeting and I just said "oh yeah that's a small thing, I'll knock it out this afternoon".
  • I'm halfway through some feature development and realize I want to make a sweeping refactor elsewhere. Toss some thoughts in the doc, and then get back to the task at hand.
  • It's the end of the day and I have to switch my brain into "feed small children" mode, thus obliterating everything work-related from my short term memory. When I open things up the next day and know exactly what the next thing to dive into was.
  • I'm preparing for a big enough refactor and I can't hold it all in my brain at once. What I'd give to have an interactive 3D playground for brain thoughts, but in the meantime a 2D text file isn't a terrible way to plan out dev work.

playground

Sometimes you need more than some human words in a markdown file to move an idea along. This is where my playground directory comes in. I can load this directory up with code that's related to a given project and keep it out of the git history. Because who doesn't like a place to play around.

I find that this directory is more useful for long running maintenance projects over fast moving greenfield ones. On the maintenance projects, I tend to find myself assembling a pile of scripts and experiments for various situations:

  • The client requests a one-time obscure data export. Whip up some CSV generation code and save that code in the playground directory.
  • The client requests a different obscure data export. Pull up the last time you did something vaguely similar and save yourself the startup time.
  • A batch of data needs to be imported just once. Might as well stash that in the chance that "just once" is actually "just a few times".
  • Kicking the tires on an integration with a third party service.

Some of these playground files end up being useful more times than I can count (eg: the ever-changing user_export.rb script). Some items get promoted into application code, which is always fun. But most files here serve their purpose and then wither away. And that's fine. It's a playground, anything goes.

Wrapping up

Having a personal space for project-specific notes and code has been helpful to me over the years as a developer on multiple projects. If you have your own organizational trick, or just want to brag about how you memorize everything without any markdown files, let me know in the comments below!




git

Getting My Butt in Gear with Digital Strategy School!

I have been running CMD+Shift Design since 2008. In those 7 years I learned a lot, I made a lot of mistakes, found some amazing clients, did some really fun projects and made some good money. I’ve had ups and downs and these past 2 years have been tough… really tough. Part of it has […]




git

5 Essential git Commands and Utilities

For many of us, git and GitHub play a huge role in our development workflows. Whenever we have a tool that we need to use often, the more fine-tuned we can make that tool, the faster we can get things done. The following are five git commands or helpers that can make your developer life […]

The post 5 Essential git Commands and Utilities appeared first on David Walsh Blog.




git

Detect git Directory with Bash

One interesting aspect of working at Mozilla is that Firefox lives in a mercurial repository while several other projects live on GitHub in a git repository. While most focus on either Firefox or another project, I switch between both, leaving me running git commands inside the mercurial repository and hg commands inside git repos. It’s […]

The post Detect git Directory with Bash appeared first on David Walsh Blog.




git

Tips for Digitizing and Organizing Old Photos

Technology continues to transform the world at a mind-numbing pace. Every year it seems, new technologies emerge that put our traditional ways of doing things to shame. Some of these methods are inherently superior, such as the movement toward digital media. While you might not be able to physically feel it in the palms of your hands, having digital media can ensure that you never lose pictures, photos and other forms of media. Most people have old photos laying around that they’d like to ensure last forever, but they haven’t taken the time to digitize and organize them. We’ll review some tips on how to digitize and organize your old photos so that they stand the test of time. Procure a Capture Solution There are a few different ways in which you can begin the process of digitizing your old photos. The first solution is through the use of a ... Read more

The post Tips for Digitizing and Organizing Old Photos appeared first on Digital Photography Tutorials.




git

Top 15 Digital Scrapbooking Downloads (Free & Paid)

Scrapbooking can be a fun way to capture important moments in life and with our list of the Top 15 Scrapbooking Resources, you can start right away!




git

Why Use A Digital Marketing Agency?

Outsourcing your marketing when you're running a small or medium sized business is often seen as an expensive option, one that can be done yourself. It might even be seen as something that's...




git

Global Gitignore Files Are Cool and So Are You

Setting it up

First, here's the config setup you need to even allow for such a radical concept.

  1. Define the global gitignore file as a global Git configuration:

    git config --global core.excludesfile ~/.gitignore
    

    If you're on OSX, this command will add the following config lines in your ~/.gitconfig file.

    [core]
      excludesfile = /Users/triplegirldad/.gitignore
    
  2. Load that ~/.gitignore file up with whatever you want. It probably doesn't exist as a file yet so you might have to create it first.

Harnessing its incredible power

There are only two lines in my global gitignore file and they are both fairly useful pretty much all the time.

$ cat ~/.gitignore
TODO.md
playground

This 2 line file means that no matter where I am, what project I'm working on, where in the project I'm doing so, I have an easy space to stash notes, thoughts, in progress ideas, spikes, etc.

TODO.md

More often than not, I'm fiddling around with a TODO.md file. Something about writing markdown in your familiar text editor speaks to my soul. It's quick, it's easy, you have all the text editing tricks available to you, and it never does anything you wouldn't expect (looking at you auto-markdown-formatting editors). I use one or two # for headings, I use nested lists, and I ask for nothing more. Nothing more than more TODO.md files that is!

In practice I tend to just have one TODO.md file per project, right at the top, ready to pull up in a few keystrokes. Which I do often. I pull this doc up if:

  • I'm in a meeting and I just said "oh yeah that's a small thing, I'll knock it out this afternoon".
  • I'm halfway through some feature development and realize I want to make a sweeping refactor elsewhere. Toss some thoughts in the doc, and then get back to the task at hand.
  • It's the end of the day and I have to switch my brain into "feed small children" mode, thus obliterating everything work-related from my short term memory. When I open things up the next day and know exactly what the next thing to dive into was.
  • I'm preparing for a big enough refactor and I can't hold it all in my brain at once. What I'd give to have an interactive 3D playground for brain thoughts, but in the meantime a 2D text file isn't a terrible way to plan out dev work.

playground

Sometimes you need more than some human words in a markdown file to move an idea along. This is where my playground directory comes in. I can load this directory up with code that's related to a given project and keep it out of the git history. Because who doesn't like a place to play around.

I find that this directory is more useful for long running maintenance projects over fast moving greenfield ones. On the maintenance projects, I tend to find myself assembling a pile of scripts and experiments for various situations:

  • The client requests a one-time obscure data export. Whip up some CSV generation code and save that code in the playground directory.
  • The client requests a different obscure data export. Pull up the last time you did something vaguely similar and save yourself the startup time.
  • A batch of data needs to be imported just once. Might as well stash that in the chance that "just once" is actually "just a few times".
  • Kicking the tires on an integration with a third party service.

Some of these playground files end up being useful more times than I can count (eg: the ever-changing user_export.rb script). Some items get promoted into application code, which is always fun. But most files here serve their purpose and then wither away. And that's fine. It's a playground, anything goes.

Wrapping up

Having a personal space for project-specific notes and code has been helpful to me over the years as a developer on multiple projects. If you have your own organizational trick, or just want to brag about how you memorize everything without any markdown files, let me know in the comments below!




git

15 Digital Products That Web Designers Can Create and Sell

There are a number of different ways to make money as a web designer aside from simply creating websites for clients. Many freelancers choose to supplement their income from client work by doing some...

Click through to read the rest of the story on the Vandelay Design Blog.




git

Global Gitignore Files Are Cool and So Are You

Setting it up

First, here's the config setup you need to even allow for such a radical concept.

  1. Define the global gitignore file as a global Git configuration:

    git config --global core.excludesfile ~/.gitignore
    

    If you're on OSX, this command will add the following config lines in your ~/.gitconfig file.

    [core]
      excludesfile = /Users/triplegirldad/.gitignore
    
  2. Load that ~/.gitignore file up with whatever you want. It probably doesn't exist as a file yet so you might have to create it first.

Harnessing its incredible power

There are only two lines in my global gitignore file and they are both fairly useful pretty much all the time.

$ cat ~/.gitignore
TODO.md
playground

This 2 line file means that no matter where I am, what project I'm working on, where in the project I'm doing so, I have an easy space to stash notes, thoughts, in progress ideas, spikes, etc.

TODO.md

More often than not, I'm fiddling around with a TODO.md file. Something about writing markdown in your familiar text editor speaks to my soul. It's quick, it's easy, you have all the text editing tricks available to you, and it never does anything you wouldn't expect (looking at you auto-markdown-formatting editors). I use one or two # for headings, I use nested lists, and I ask for nothing more. Nothing more than more TODO.md files that is!

In practice I tend to just have one TODO.md file per project, right at the top, ready to pull up in a few keystrokes. Which I do often. I pull this doc up if:

  • I'm in a meeting and I just said "oh yeah that's a small thing, I'll knock it out this afternoon".
  • I'm halfway through some feature development and realize I want to make a sweeping refactor elsewhere. Toss some thoughts in the doc, and then get back to the task at hand.
  • It's the end of the day and I have to switch my brain into "feed small children" mode, thus obliterating everything work-related from my short term memory. When I open things up the next day and know exactly what the next thing to dive into was.
  • I'm preparing for a big enough refactor and I can't hold it all in my brain at once. What I'd give to have an interactive 3D playground for brain thoughts, but in the meantime a 2D text file isn't a terrible way to plan out dev work.

playground

Sometimes you need more than some human words in a markdown file to move an idea along. This is where my playground directory comes in. I can load this directory up with code that's related to a given project and keep it out of the git history. Because who doesn't like a place to play around.

I find that this directory is more useful for long running maintenance projects over fast moving greenfield ones. On the maintenance projects, I tend to find myself assembling a pile of scripts and experiments for various situations:

  • The client requests a one-time obscure data export. Whip up some CSV generation code and save that code in the playground directory.
  • The client requests a different obscure data export. Pull up the last time you did something vaguely similar and save yourself the startup time.
  • A batch of data needs to be imported just once. Might as well stash that in the chance that "just once" is actually "just a few times".
  • Kicking the tires on an integration with a third party service.

Some of these playground files end up being useful more times than I can count (eg: the ever-changing user_export.rb script). Some items get promoted into application code, which is always fun. But most files here serve their purpose and then wither away. And that's fine. It's a playground, anything goes.

Wrapping up

Having a personal space for project-specific notes and code has been helpful to me over the years as a developer on multiple projects. If you have your own organizational trick, or just want to brag about how you memorize everything without any markdown files, let me know in the comments below!




git

Multi-task pre-training of deep neural networks for digital pathology. (arXiv:2005.02561v2 [eess.IV] UPDATED)

In this work, we investigate multi-task learning as a way of pre-training models for classification tasks in digital pathology. It is motivated by the fact that many small and medium-size datasets have been released by the community over the years whereas there is no large scale dataset similar to ImageNet in the domain. We first assemble and transform many digital pathology datasets into a pool of 22 classification tasks and almost 900k images. Then, we propose a simple architecture and training scheme for creating a transferable model and a robust evaluation and selection protocol in order to evaluate our method. Depending on the target task, we show that our models used as feature extractors either improve significantly over ImageNet pre-trained models or provide comparable performance. Fine-tuning improves performance over feature extraction and is able to recover the lack of specificity of ImageNet features, as both pre-training sources yield comparable performance.




git

Generative Adversarial Networks in Digital Pathology: A Survey on Trends and Future Potential. (arXiv:2004.14936v2 [eess.IV] UPDATED)

Image analysis in the field of digital pathology has recently gained increased popularity. The use of high-quality whole slide scanners enables the fast acquisition of large amounts of image data, showing extensive context and microscopic detail at the same time. Simultaneously, novel machine learning algorithms have boosted the performance of image analysis approaches. In this paper, we focus on a particularly powerful class of architectures, called Generative Adversarial Networks (GANs), applied to histological image data. Besides improving performance, GANs also enable application scenarios in this field, which were previously intractable. However, GANs could exhibit a potential for introducing bias. Hereby, we summarize the recent state-of-the-art developments in a generalizing notation, present the main applications of GANs and give an outlook of some chosen promising approaches and their possible future applications. In addition, we identify currently unavailable methods with potential for future applications.




git

Digital Twin: Enabling Technologies, Challenges and Open Research. (arXiv:1911.01276v3 [cs.CY] UPDATED)

Digital Twin technology is an emerging concept that has become the centre of attention for industry and, in more recent years, academia. The advancements in industry 4.0 concepts have facilitated its growth, particularly in the manufacturing industry. The Digital Twin is defined extensively but is best described as the effortless integration of data between a physical and virtual machine in either direction. The challenges, applications, and enabling technologies for Artificial Intelligence, Internet of Things (IoT) and Digital Twins are presented. A review of publications relating to Digital Twins is performed, producing a categorical review of recent papers. The review has categorised them by research areas: manufacturing, healthcare and smart cities, discussing a range of papers that reflect these areas and the current state of research. The paper provides an assessment of the enabling technologies, challenges and open research for Digital Twins.




git

Pricing under a multinomial logit model with non linear network effects. (arXiv:2005.03352v1 [cs.GT])

We study the problem of pricing under a Multinomial Logit model where we incorporate network effects over the consumer's decisions. We analyse both cases, when sellers compete or collaborate. In particular, we pay special attention to the overall expected revenue and how the behaviour of the no purchase option is affected under variations of a network effect parameter. Where for example we prove that the market share for the no purchase option, is decreasing in terms of the value of the network effect, meaning that stronger communication among costumers increases the expected amount of sales. We also analyse how the customer's utility is altered when network effects are incorporated into the market, comparing the cases where both competitive and monopolistic prices are displayed. We use tools from stochastic approximation algorithms to prove that the probability of purchasing the available products converges to a unique stationary distribution. We model that the sellers can use this stationary distribution to establish their strategies. Finding that under those settings, a pure Nash Equilibrium represents the pricing strategies in the case of competition, and an optimal (that maximises the total revenue) fixed price characterise the case of collaboration.





git

Smell the digital roses. It’s time for another Virtual First Friday Art Walk

Another First Friday is here, and you can correctly assume that it will be all online once again. The May 1 Virtual First Friday is from 10 am to midnight.…



  • Arts & Culture

git

Method and apparatus for detecting a parity error in a sequence of DQPSK symbols of a digital transmission system

The present disclosure relates to a method for detecting a parity error in a sequence of DQPSK symbols of a digital transmission system, comprising determining a first demodulated symbol r1; determining a second demodulated symbol r2; determining a first parity symbol p1; determining a second parity symbol p2; determining a super-parity symbol q1; and detecting a parity error in the sequence of DQPSK symbols by comparing a combination of the first parity symbol p1 and the second parity symbol p2 against the super-parity symbol q1, wherein a parity between two DQPSK symbols describes a phase difference between the two DQPSK symbols.




git

Phase-to-amplitude converter for direct digital synthesizer (DDS) with reduced AND and reconstructed ADD logic arrays

A sine wave generator for a Direct Digital Synthesizer (DDS) converts a digital phase input into a digital sine wave output. Sine values and slopes are stored in read-only memory (ROM) for coarse upper phase bits in a first quadrant. A quadrant folder and phase splitter reflects and inverts values from the first quadrant to generate amplitudes for all four quadrants. Each sine value and slope is stored for a range of lower phase bits. A Delta bit separates upper and lower phase bits. Delta conditionally inverts the lower phase bits, the sine value, and the final polarity. A reduced AND logic array multiplies the slope by the conditionally inverted lower phase bits. A reconstructed ADD logic array then adds the conditionally inverted sine value. The conditionally inverted polarity is added to generate the final sine value. Sine generation logic is streamlined with conditional inversion based on the Delta bit.




git

Method and apparatus for generating metadata for digital content

A method and an apparatus for generating metadata for digital content are described, which allow to review the generated metadata already in course of ongoing generation of metadata. The metadata generation is split into a plurality of processing tasks, which are allocated to two or more processing nodes. The metadata generated by the two or more processing nodes is gathered and visualized on an output unit.




git

Reactor and agitator useful in a process for making 1-chloro-3,3,3-trifluoropropene

Disclosed is a reactor and agitator useful in a high pressure process for making 1-chloro-3,3,3-trifluoropropene (1233zd) from the reaction of 1,1,1,3,3-pentachloropropane (240fa) and HF, wherein the agitator includes one or more of the following design improvements: (a) double mechanical seals with an inert barrier fluid or a single seal;(b) ceramics on the rotating faces of the seal;(c) ceramics on the static faces of seal;(d) wetted o-rings constructed of spring-energized Teflon and PTFE wedge or dynamic o-ring designs; and(e) wetted metal surfaces of the agitator constructed of a corrosion resistant alloy.




git

Implementation of multi-tasking on a digital signal processor with a hardware stack

The disclosure relates to the implementation of multi-tasking on a digital signal processor. Blocking functions are arranged such that they do not make use of a processor's hardware stack. Respective function calls are replaced with a piece of inline assembly code, which instead performs a branch to the correct routine for carrying out said function. If a blocking condition of the blocking function is encountered, a task switch can be done to resume another task. Whilst the hardware stack is not used when a task switch might have to occur, mixed-up contents of the hardware stack among function calls performed by different tasks are avoided.




git

Dynamic energy savings for digital signal processor modules using plural energy savings states

In an example embodiment, there is described herein an apparatus comprising an interface for communicating with a plurality of digital signal processors and logic operable to send and receive data via the interface. The logic is configured to determine a first set of digital signal processors to be maintained in a ready state, a second set of digital signal processors to be maintained in a first energy saving state, and a third set of digital signal processors to be maintained in a second energy saving state.




git

Firmware update method and apparatus of set-top box for digital broadcast system

A firmware update method and apparatus of a set-top box for a digital broadcast system is provided. A firmware update method of a set-top box for a digital broadcast system includes determining whether a newly received Code Version Table (CVT) following a public CVT which has been previously received and stored is the public CVT or a filtering CVT; and updating, when the newly received CVG is the filtering CVT, the firmware of the set-top box with a filtering firmware indicated by the filtering CVT.




git

Data mining in a digital map database to identify blind intersections along roads and enabling precautionary actions in a vehicle

Disclosed is a feature for a vehicle that enables taking precautionary actions in response to conditions on the road network around or ahead of the vehicle, in particular, a blind intersection along a section of road. A database that represents the road network is used to determine locations where a blind intersection is located along a section of road. Then, precautionary action data is added to the database to indicate a location at which a precautionary action is to be taken about the blind intersection located along the section of road. A precautionary action system installed in a vehicle uses this database, or a database derived therefrom, in combination with a positioning system to determine when the vehicle is at a location that corresponds to the location of a precautionary action. When the vehicle is at such a location, a precautionary action is taken by a vehicle system as the vehicle is approaching a blind intersection.




git

Digital circuit verification monitor

A method, a system and a computer readable medium for providing information relating to a verification of a digital circuit. The verification may be formal verification and comprise formally verifying that a plurality of formal properties is valid for a representation of the digital circuit. The method comprises replacing at least a first input value relating to the representation of the digital circuit by a first free variable, determining if at least one of the plurality of formal properties is valid or invalid after replacing the first input value by the first variable and indicating if the at least one of the plurality of formal property is valid or invalid. The use of a free or open variable that has not determined value can be directly in the description or representation of the digital circuit. It is not necessary to insert errors or to apply an error model.




git

System and method for automated simulator assertion synthesis and digital equivalence checking

A system, method, and computer program product for automatically generating equivalent assertions in different forms for different verification tools, which may be analog or digital. A user submits a set of logic assertions that, if unclocked, are converted to clocked assertions by generating and skewing clocks to ensure simulator uniformity. A stimulus is generated, perhaps at random, or input. A test bench is either input or synthesized. For each verification tool, the test bench is simulated and simulation results are captured. An assertion status difference engine evaluates result differences between the verification tools, and identifies and outputs differences indicating a significant inconsistency. Errors in verification tool implementation and user assertion coding can be detected. The simulators used may include SPICE and Verilog, or any other simulators that differ in type, simulation algorithm, input format, or vendor implementation.




git

Email administration for rendering email on a digital audio player

Methods, systems, and computer program products are provided for email administration for rendering email on a digital audio player. Embodiments include retrieving an email message; extracting text from the email message; creating a media file; and storing the extracted text of the email message as metadata associated with the media file. Embodiments may also include storing the media file on a digital audio player and displaying the metadata describing the media file, the metadata containing the extracted text of the email message.




git

Interfaces for digital media processing

APIs discussed herein promote efficient and timely interoperability between hardware and software components within the media processing pipelines of media content players. A PhysMemDataStructure API facilitates a hardware component's direct access to information within a memory used by a software component, to enable the hardware component to use direct memory access techniques to obtain the contents of the memory, instead of using processor cycles to execute copy commands. The PhysMemDataStructure API exposes one or more fields of data structures associated with units of media content stored in a memory used by a software component, and the exposed fields store information about the physical properties of the memory locations of the units of media content. SyncHelper APIs are used for obtaining information from, and passing information to, hardware components, which information is used to adjust the hardware components' timing for preparing media samples of synchronously-presentable media content streams.




git

System and method for providing digital messaging services

An exemplary embodiment of the invention relates to a system and method for providing digital messaging services received from multiple sources over a communications network. The system includes a client system, including a display screen coupled to a communications link; a workstation including a web browser, a memory, and a processor, said workstation coupled to said communications link; a hosting system, including a graphics server, a content server, and a scheduling server, each in communication with each other via a communications link; and a workstation and data storage device coupled to the communications link; and a data storage device for storing data utilized by said hosting system. The client system requests and receives digital messaging services from said hosting system under a subscription agreement. Digital messaging services include advertisements procured from said client system, and one or more local content providers, national advertisers, local advertisers, corporate marketing groups, and advertising agencies. Interactive digital messaging services are also available through the present invention. A user accesses these services via a variety of input devices; such as a bar code scanner, a wireless telephone or personal digital assistant, a kiosk with touch screen design, microphone, or other similar input device.




git

Method for controlling content and digital device using the same

A method and device for controlling content that includes plural display pages in a sequence, the method including: displaying a current page included in the content; receiving a user input to or above a display screen of the display unit for changing from the current page to another page of the content; extracting fingerprint information from the user input; determining whether the content of the another page is or is not accessible based on the extracted fingerprint information; if all of the content of the another page is determined to be accessible based on the extracted fingerprint information, displaying the another page; and if any of the content of the another page is determined not to be accessible based on the extracted fingerprint information, displaying a page following the current page without displaying content of the another page that was determined not to be accessible.




git

Digital flowmeter

A control and measurement system for a coriolis flowmeter having a flowtube, a driver adapted to vibrate the flowtube, and a pair of sensors adapted to generate signals indicative of movement of the flowtube when it is being vibrated by the driver, wherein the sensors are positioned relative to one another so the signals from the sensors are indicative of a mass flow rate of fluid through the flowtube. A digital drive signal generator is adapted to generate a variable digital drive signal for controlling operation of the driver. The digital drive signal generator can be adapted to cause the driver to resist motion of the flowtube during a first time period and amplify motion of the flowtube during a second time period. The digital drive signal generator can also be adapted to initiate motion of the flowtube by sending one or more square wave signals to the driver.




git

Digital flowmeter

A control and measurement system for a coriolis flowmeter having a flowtube, a driver adapted to vibrate the flowtube, and a pair of sensors adapted to generate signals indicative of movement of the flowtube when it is being vibrated by the driver, wherein the sensors are positioned relative to one another so the signals from the sensors are indicative of a mass flow rate of fluid through the flowtube. A digital drive signal generator is adapted to generate a variable digital drive signal for controlling operation of the driver. The digital drive signal generator can be adapted to cause the driver to resist motion of the flowtube during a first time period and amplify motion of the flowtube during a second time period. The digital drive signal generator can also be adapted to initiate motion of the flowtube by sending one or more square wave signals to the driver.




git

Method and an apparatus/universal combine for agitation of liquids

A method of mixing together liquids or liquid/solid combinations, and mixing apparatus/universal combine utilizing a vertical spinning container or vessel having a rib, or a cross rib in its bottom wall. The container is spun about a vertical axis with no wobbling component to the motion. Meshed elements are used for high shear mixing. Start/stop routines, and variable acceleration/speed values are used, to facilitate complete mixing. Use of ‘impeller’ blade stirrers is completely eliminated.




git

Tank agitation system with moveable shaft support

An apparatus for containing and mixing a load of liquids and solids is disclosed. The apparatus includes an elongated tank, which includes a lower portion and an upper portion. The apparatus further includes an elongated rotatable shaft within the tank. At least one blade is connected to the shaft and is configured to mix the liquids and solids when the shaft is rotated. The apparatus also includes a shaft support configured for maintaining the shaft in a rotatable manner within the tank. The shaft support is selectively moveable in a manner permitting the shaft to move in an upward direction from the lower portion toward the upper portion, and in a downward direction from the upper portion toward the lower portion. An is contained with the tank for moving the shaft support in the upward direction and in the downward direction.




git

Fluid agitation apparatus for reducing temperature fluctuation and thermostatic apparatus

Provided are a fluid agitation apparatus using a structure which is simple in shape and short in a fluid passage direction without a movable part so as to produce a sufficient effect from the viewpoint of reducing temperature fluctuation, and a thermostatic apparatus using the fluid agitation apparatus. The fluid agitation apparatus is installed in a fluid passage and includes, in an order from an upstream side thereof: a dividing part for dividing a flow of a fluid into a plurality of flows; a circumvolving part for circumvolving the fluid about an axis in a flow direction of the fluid; and an accelerating part for increasing a flow rate of the fluid.




git

Agitator for abrasive media

An agitator, particularly for abrasive media includes a support disk to which agitator blades are connected substantially perpendicular to the support disk. The blades are arranged substantially in a radial direction. The support disk also includes a hub that receives an agitator shaft which is preferably motor-driven. The trailing faces of the blades of the agitator and/or the area of the blade connections to the support disk are designed to largely prevent vortex shedding. This is accomplished by implementing a specific geometry for the agitator blades, the support disk, and the connection of the blades to the support disk.




git

Hollow bolt comprising a longitudinal bore

A process for producing hollow bolts including a longitudinal bore with the hollow bolts being provided with circumferential notches. The hollow bolts are provided with longitudinal grooves extending between elevations determining the bolt diameter, wherein circumferential notches are rolled onto the hollow bolts provided with the longitudinal grooves and the elevations, the longitudinal grooves being of such cross-section that some of the material displaced during rolling-on of the notches flows into the longitudinal grooves.




git

Method and apparatus for reconditioning digital discs

An automated method for reconditioning a plurality of digital discs within a reconditioning apparatus is disclosed. The method comprises holding the digital discs in a load area, and then transferring each of the digital discs from the load area to at least one workstation with a disc transfer mechanism. The method also comprises reconditioning each of the digital discs transferred to the workstation with at least one worktool operable to remove a portion of the protective coating of each of the digital discs without removal of the data underlying the protective coating. The method further comprises transferring each of the digital discs from the workstation to an unload area with the disc transfer mechanism, and then holding the digital discs in the unload area for manual retrieval. Advantageously, the digital discs may be automatically reconditioned within the reconditioning apparatus without manual manipulation of the digital discs during the reconditioning process. Various exemplary embodiments of the reconditioning apparatus and associated method are provided.




git

Head tool changer for use with deposition-based digital manufacturing systems

A head tool changer for use with a deposition-based digital manufacturing system, the head tool changer comprising a tooling unit configured to retain a deposition head, a grip unit configured to engage with tooling unit and to relay electrical power to the tooling unit, and a master unit operably mounted to a gantry and configured to engage with the tooling unit and to relay electrical power to the tooling unit.




git

Method and apparatus for controlling update of digital pre-distortion coefficient

A method and apparatus for controlling update of digital pre-distortion (DPD) coefficient is provided. The apparatus is applicable to a digital power control system, wherein the apparatus comprises: an update controlling unit configured to determine a group of fully-trained DPD coefficients among a plurality of DPD coefficients; and a DPD coefficient generating unit configured to update adaptively the group of fully-trained DPD coefficients according to the result of judgment of the update controlling unit. The DPD coefficients are allowed to be updated after being judged as being able to be fully trained according to power distribution information of DPD input signals, or according to address distribution information of an LUT, or according to average power of output of an HPA; otherwise, they may not be updated, thereby efficiently preventing DPD abnormality resulted from unfull training of coefficients in being updated.




git

Providing digital data services in optical fiber-based distributed radio frequency (RF) communication systems, and related components and methods

Optical fiber-based distributed communications systems that provide and support both RF communication services and digital data services are disclosed herein. The RF communication services and digital data services can be distributed over optical fiber to client devices, such as remote antenna units for example. In certain embodiments, digital data services can be distributed over optical fiber separate from optical fiber distributing RF communication services. In other embodiments, digital data services can be distributed over common optical fiber with RF communication services. For example, digital data services can be distributed over common optical fiber with RF communication services at different wavelengths through wavelength-division multiplexing (WDM) and/or at different frequencies through frequency-division multiplexing (FDM). Power distributed in the optical fiber-based distributed communications system to provide power to remote antenna units can also be accessed to provide power to digital data service components.




git

Hybrid digital and channel microfluidic devices and methods of use thereof

The present invention provides a hybrid digital and channel microfluidic device in the form of an integrated structure in which a droplet may be transported by a digital microfluidic array and transferred to a microfluidic channel. In one aspect of the invention, a hybrid device comprises a first substrate having a digital microfluidic array capable of transporting a droplet to a transfer location, and a second substrate having a microfluidic channel. The first and second substrates are affixed to form a hybrid device in which an opening in the microfluidic channel is positioned adjacent to the transfer location, so that a droplet transported to the transfer location contacts the channel opening and may enter the channel. The invention also provides methods of performing separations using a hybrid digital and channel microfluidic device and methods of assembling a hybrid digital microfluidic device.




git

Measuring apparatus and referencing method for a digital laser distance meter, and laser distance meter

A handheld distance measuring instrument includes a first emission device, a first reception device and a second reception device. The first emission device is configured to emit an optical measurement radiation onto a target object. The first reception device is configured to detect the radiation returning from the target object. The second reception device is configured in order to detect a reference radiation internal to the instrument. The reception devices respectively include a first detector unit, a second detector unit, a first time measurement unit, and a second time measurement unit. The first time measurement unit is configured to be connected selectively to the first detector unit and to the second detector unit. The second time measurement unit is configured to be connected selectively to the first detector unit and to the second detector unit.




git

Digital pathology system

The present invention may include an illumination source; a TDI sensor having a plurality of rows of TDI pixels, wherein each of the TDI pixels have a 1:1 aspect ratio; a multicolor filter contacted to the surface of the TDI sensor, wherein the multicolor filter has alternating sections of a first color filter, a second color filter, and at least a third color, wherein adjacent rows of TDI pixels are grouped in order to form a plurality of rows of integrated multicolor pixels; an objective having a first end positioned proximate to the specimen; a second lens configured to focus light from the image path onto the TDI sensor; and an anamorphic optics element configured to magnify an image of the one or more specimens such that the image is magnified by a factor of three along a direction orthogonal to an integrating direction of the TDI sensor.




git

Applying digital frequency offset to timing loop

A system for providing an accumulated phase to an interpolator of a read channel, the interpolator configured to provide a digital clock signal. A frequency accumulator is configured to generate a frequency offset based on a difference between the digital clock signal and a desired clock signal. A zero phase start module is configured to, during a zero phase start, output an incremental phase jump. A phase accumulator is configured to generate the accumulated phase based on the difference between the digital clock signal and the desired clock signal, and, during the zero phase start, the incremental phase jump output by the zero phase start module, or the frequency offset generated by the frequency accumulator or a predetermined frequency offset.




git

Production of tissue engineered digits and limbs

The invention pertains to methods of producing artificial composite tissue constructs that permit coordinated motion. Biocompatable structural matrices having sufficient rigidity to provide structural support for cartilage-forming cells and bone-forming cells are used. Biocompatable flexible matrices seeded with muscle cells are joined to the structural matrices to produce artificial composite tissue constructs that are capable of coordinated motion.




git

Advertisement delivering system based on digital television system and mobile communication device

A digital television system is connected to a mobile computing and communication device through an ad hoc communication link. A program broadcasted by the television system includes a plurality frames delivered in a sequential manner. A user can freeze a frame by employing the mobile device. The frame can then be transmitted to the mobile device and be redisplayed on the mobile device. The redisplayed frame includes visible symbols pointing to displayed items associated with advertising messages. The frame can also be stored in a photograph folder for the user to view the frame and associated advertising messages in a later time.