# Introduction to Sinusoidal Signal Processing with Scilab

August 30, 2018 by Robert Keim## This article discusses basic signal-processing tasks that can be performed using a free and open source alternative to MATLAB.

This article discusses basic signal-processing tasks that can be performed using a free and open source alternative to MATLAB.

### Scilab vs. MATLAB

I’ve done quite a bit of work with MATLAB over the years, and it is undoubtedly a powerful tool that can simplify and accelerate a wide variety of engineering tasks. However, developing software of this quality is by no means inexpensive, and I wouldn’t be surprised to learn that the cost of a standard MATLAB license doesn’t fit within the budgetary constraints of numerous entrepreneurs, consultants, startups, and small engineering firms. It turns out, though, that there is an alternative to MATLAB that is completely free called Scilab.

In my experience with Scilab, it is very capable and reasonably user-friendly. Another advantage is that the Scilab interface is similar to the MATLAB interface, so if you have experience with MATLAB (maybe from your days as a student or an employee of a large company), Scilab should feel somewhat familiar.

### Working with Digitized Sinusoids

In the world of signal processing, sinusoids are everywhere. This is as true in the digital realm as it is in the analog realm, and consequently it is important to thoroughly understand the nature of a digitized sinusoid.

Both analog and digital sine waves have amplitude, frequency, and phase. For this article, we don’t need to concern ourselves with phase, and amplitude doesn’t really change when you move from analog to digital; frequency, on the other hand, requires some attention. In the analog domain, frequency specifies the number of cycles with respect to time. Units of time are the same always and everywhere—e.g., 100 Hz (= 100 cycles __per second__) means the same thing in every engineering project. In the digital domain, frequency loses its reference to an unchanging unit of time. Instead, we have individual amplitude values that must be interpreted according to the sample rate. This can lead to confusion for two reasons: 1) many different sample rates are used, and 2) sample-rate information is not contained within the series of amplitude values.

#### Sine Generation in Scilab

Let’s explore this issue through an example. We’re going to use Scilab to create one cycle of a sine wave that has 100 samples per cycle. This is the first command:

n = 0:99;

We just created an array that begins at 0 and ends at 99. You can look in the “Variable Browser” to confirm that *n* is a one-dimensional array with a length of 100.

The array *n* is the digital equivalent of *t* (i.e., time) in the typical sin(ωt) expression that we use in the analog domain. Next, I’ll enter the following two commands:

y = sin(n); plot(y)

This is the result:

It looks terrible, I know, and it’s clearly wrong—we wanted one cycle composed of 100 samples. Let’s think about why this happened:

- Sine is simply a function that operates on an argument.
- The sine function does not generate unique values for every argument. Rather, the values repeat when the argument changes by 2π: sin(0) = sin(2π) = sin(4π) = sin(6π)....
- Thus, one cycle of sine values corresponds to a 2π range of argument values.
- This means that to generate one cycle of sine values, we need to
*modify the argument array so that it extends from 0 to 2**π*.

The command **y = sin(n)** doesn’t produce the desired waveform because the argument given to the sine function is an array that extends from 0 to 99. The solution is to divide *n* by the desired number of samples per cycle, which in this case is 100, and also multiply it by 2π:

y = sin(2*%pi*n/100);

You can readily confirm that this will work: if *n* is zero, the entire argument is zero; if *n* is 100, the argument is (2π × 100/100) = 2π; and all the numbers in between are scaled accordingly. Thus, we have reduced the argument range to 2π, and we are still producing 100 samples. (**Note:** I realize that in this case *n* does not extend to 100, but if it did, we would want the value 100 to be the first sample in the second cycle. In other words, the first cycle is covered by the 100 values from 0 to 99, the second cycle would be covered by the 100 values from 100 to 199, and so forth.) Here is the result:

plot(y)

#### Refining the Plot

There’s still something not quite right about the plot. We know that sin(0) = 0, but in the plot, the waveform has a value of 0 for a horizontal-axis value of 1. In other words, the waveform is shifted one sample to the right. This occurs because we didn’t specify a list of horizontal-axis values that correspond to the vertical-axis values contained in the array *y*. If we tell Scilab **plot(y)**, it uses default values for the horizontal axis, and apparently these default values start at one.

The command **y = sin(2*%pi*n/100)** generates *y* values that correspond to the numbers in the array *n*. If we want the plot to maintain this relationship between *y* and *n*, we can use the following command:

plot(n, y)

### Incorporating Frequency and Sample Rate

When we’re working with real sinusoidal signals, we generally think in terms of signal frequency (in the analog domain) and sampling frequency (in the digital domain). Thus, we need to integrate these parameters into the purely mathematical ideas presented thus far.

Fortunately, this is not difficult. We saw above that the argument for the sine function needs to include a factor of (2π/samples per cycle). We can calculate samples per cycle for real-world signals as follows:

$$\text{samples per cycle}=\frac{\text{sampling frequency}}{\text{signal frequency}}$$

Let’s say we have a system that digitizes a 6 kHz audio signal and a separate 2 kHz audio signal. The sampling frequency is 44.1 kHz, and the ADC fills a 50-sample buffer. The following sequence of Scilab commands can be used to generate values that resemble the data produced by the actual system.

SignalFrequency_1 = 6e3; SignalFrequency_2 = 2e3; SamplingFrequency = 44.1e3; n = 0:49; Signal_1 = sin(2*%pi*n / (SamplingFrequency/SignalFrequency_1)); Signal_2 = sin(2*%pi*n / (SamplingFrequency/SignalFrequency_2)); plot(n, Signal_1) plot(n, Signal_2)

### Conclusion

This article provided a brief introduction to the characteristics of digitized sinusoids and the techniques used to create these sinusoids in Scilab. I plan to write additional articles on Scilab-based signal processing and analysis; if there’s a specific topic that you think would be interesting, feel free to mention it in the comments.

6 CommentsPlease post on article on

1) MATLAB vs Octave vs Scilab

2) what extra a MATLAB programmer need to learn(syntax-wise) in order to use other two platforms

We use Scilab quite a bit. This is a very nice tutorial. I like signal manipulations. Do you have a few methods to determine phase differences between say two or three signals? One I have been keen to try is cross-correlation. I’ve seen it being used on a eval kit with two microphones to determine which direction sound was coming from. Very cool. But I’d like to see how one can determine the phase and then correct the signal that is out of phase in one go.

Thanks. For me, this post is just in time. Just started making my hands dirty on Signal processing, Was thinking of Installing Matlab, Then came across this article. Looking forward.

Some time ago I came across the same question, and found out the following

SCILAB pros (against MATLAB):

tiny installation program, portable, no registration online required, free as in $0.0.

MATLAB pros (against SCILAB):

1.- the HELP file is really really helpful, a lot of work has been put building an is being put updating such comprehensive and at the same time deep in detail and rich in examples help. Scilab lacks such help, I spent @3 months comitting to Scilab and had to give up prercisely because of the lack of literature, online support, or simply a wide enough community to turn to with question to fix jammed tasks.

2.- The toolboxes: Again, there’s a cumulative organized effort to build specific tools that is far more robust from Mathworks, than from whoever is behind Scilab.

3.- The myth of the price: for £50.- you can get a student license, and even if you are not in colleague, Mathworks tags the same price on the ‘home’ version, that is basically the same as the student version, for those hobbyists who want to learn at their own pace or simply solve tasks at home without the chores of attending classroom or keeping pace with syllabus and exams.

4.- Scilab is French, MATLAB is American. I know it may sound a cliché but 1st AutoCAD was created by Autodesk, the whole industry relies on Autodesk applications the same way that 1st world relies on caffeine, cars and computers. Then products like Proengineer, Katia, et al showed up, offering competitive prices, but they were developed by European corporations Siemens (Siemens invented VAT in early XX century) to precisely avoid using American products: Boeing 747? eurobus A800. GPS? Galileo. Microsoft? or Facebook? hefty illegal fines. millions charged, for something as silly and abusive as not asking to choose what default browser.

The point is, if you want to buy US products, besides the already mentioned points that MATLAB is far more robust, has a wider community, and you can get a license for peanuts, MATLAB is the choice.

this guy .(JavaScript must be enabled to view this email address) has a free book Scliab starter ed. date Mars 2007. I also found another starter book from some one called Gonzalez in the British Library. I borrowed it, next day it was back in the returns tray.

correction: there was a book, author Calude Gomez, not helpful.

I got copy of Scilab Scicos, by Stephen Cambell slc@,ath.ncsu.edu Ramine Nikoukhah .(JavaScript must be enabled to view this email address) and Jean-Philippe Chancelier .(JavaScript must be enabled to view this email address)

Campbell is based in NCSU but Scilab comes from INRIA, French state funded, Grenoble.