| layout | title | description | categories | seriesId | seriesOrder |
|---|---|---|---|---|---|
post |
Other interesting ways of using F# at work |
Twenty six low-risk ways to use F# at work (part 5) |
Low-risk ways to use F# at work |
5 |
This post is the conclusion of the series on low-risk and incremental ways to use F# at work.
To wrap up, we'll look at a few more ways in which F# can help you with various development tasks around the edges, without impacting any core or mission critical code.
Before moving on to the content of the post, here's the full list of the twenty six ways:
Part 1 - Using F# to explore and develop interactively
1. Use F# to explore the .NET framework interactively
2. Use F# to test your own code interactively
3. Use F# to play with webservices interactively
4. Use F# to play with UI's interactively
Part 2 - Using F# for development and devops scripts
5. Use FAKE for build and CI scripts
6. An F# script to check that a website is responding
7. An F# script to convert an RSS feed into CSV
8. An F# script that uses WMI to check the stats of a process
9. Use F# for configuring and managing the cloud
Part 3 - Using F# for testing
10. Use F# to write unit tests with readable names
11. Use F# to run unit tests programmatically
12. Use F# to learn to write unit tests in other ways
13. Use FsCheck to write better unit tests
14. Use FsCheck to create random dummy data
15. Use F# to create mocks
16. Use F# to do automated browser testing
17. Use F# for Behaviour Driven Development
Part 4. Using F# for database related tasks
18. Use F# to replace LINQpad
19. Use F# to unit test stored procedures
20. Use FsCheck to generate random database records
21. Use F# to do simple ETL
22. Use F# to generate SQL Agent scripts
**Part 5: Other interesting ways of using F# **
23. Use F# for parsing
24. Use F# for diagramming and visualization
25. Use F# for accessing web-based data stores
26. Use F# for data science and machine learning
(BONUS) 27: Balance the generation schedule for the UK power station fleet
This last group of suggestions is a bit of a mish-mash I'm afraid. These are things that didn't fit into earlier posts, mostly concerning using F# for analysis and data processing.
It is surprising how often you need to parse something in the course of routine development: splitting strings at spaces, reading a CSV file, doing substitutions in a template, finding HTML links for a web crawler, parsing a query string in a URI, and so on.
F#, being an ML-derived language, is ideal for parsing tasks of all kinds, from simple regexes to full fledged parsers.
Of course, there are many off-the-shelf libraries for common tasks, but sometimes you need to write your own. A good example of this is TickSpec, the BDD framework that we saw earlier.
TickSpec needs to parse the so-called "Gherkin" format of Given/When/Then. Rather than create a dependency on another library, I imagine that it was easier (and more fun) for Phil to write his own parser in a few hundred lines. You can see part of the source code here.
Another situation where it might be worth writing your own parser is when you have some complex system, such as a rules engine, which has a horrible XML configuration format. Rather than manually editing the configuration, you could create a very simple domain specific language (DSL) that is parsed and then converted to the complex XML.
In his book on DSLs, Martin Fowler gives an example of this, a DSL that is parsed to create a state machine. And here is an F# implementation of that DSL.
For more complicating parsing tasks, I highly recommend using FParsec, which is perfectly suited for this kind of thing. For example, it has been used for parsing search queries for FogCreek, CSV files, chess notation, and a custom DSL for load testing scenarios.
Once you have parsed or analyzed something, it is always nice if you can display the results visually, rather than as tables full of data.
For example, in a previous post I used F# in conjunction with GraphViz to create diagrams of dependency relationships. You can see a sample below:
The code to generate the diagram itself was short, only about 60 lines, which you can see here.
As an alternative to GraphViz, you could also consider using FSGraph.
For more mathematical or data-centric visualizations, there are a number of good libraries:
- FSharp.Charting for desktop visualizations that is well integrated with F# scripting.
- FsPlot for interactive visualizations in HTML.
- VegaHub, an F# library for working with Vega
- F# for Visualization
And finally, there's the 800 lb gorilla -- Excel.
Using the built-in capabilities of Excel is great, if it is available. And F# scripting plays well with Excel.
You can chart in Excel, plot functions in Excel, and for even more power and integration, you have the FCell and Excel-DNA projects.
There is a lot of public data out on the web, just waiting to pulled down and loved. With the magic of type providers, F# is a good choice for direct integrating these web-scale data stores into your workflow.
Right now, we'll look at two data stores: Freebase and World Bank. More will be available soon -- see the fsharp.org Data Access page for the latest information.
The code for this section is available on github.
Freebase is a large collaborative knowledge base and online collection of structured data harvested from many sources.
To get started, just link in the type provider DLL as we have seen before.
The site is throttled, so you'll probably need an API key if you're using it a lot (api details here)
// sets the current directory to be same as the script directory
System.IO.Directory.SetCurrentDirectory (__SOURCE_DIRECTORY__)
// Requires FSharp.Data under script directory
// nuget install FSharp.Data -o Packages -ExcludeVersion
#r @"Packages\FSharp.Data\lib\net40\FSharp.Data.dll"
open FSharp.Data
// without a key
let data = FreebaseData.GetDataContext()
// with a key
(*
[<Literal>]
let FreebaseApiKey = "<enter your freebase-enabled google API key here>"
type FreebaseDataWithKey = FreebaseDataProvider<Key=FreebaseApiKey>
let data = FreebaseDataWithKey.GetDataContext()
*)Once the type provider is loaded, you can start asking questions, such as...
"Who are the US presidents?"
data.Society.Government.``US Presidents``
|> Seq.map (fun p -> p.``President number`` |> Seq.head, p.Name)
|> Seq.sortBy fst
|> Seq.iter (fun (n,name) -> printfn "%s was number %i" name n )Result:
George Washington was number 1
John Adams was number 2
Thomas Jefferson was number 3
James Madison was number 4
James Monroe was number 5
John Quincy Adams was number 6
...
Ronald Reagan was number 40
George H. W. Bush was number 41
Bill Clinton was number 42
George W. Bush was number 43
Barack Obama was number 44
Not bad for just four lines of code!
How about "what awards did Casablanca win?"
data.``Arts and Entertainment``.Film.Films.IndividualsAZ.C.Casablanca.``Awards Won``
|> Seq.map (fun award -> award.Year, award.``Award category``.Name)
|> Seq.sortBy fst
|> Seq.iter (fun (year,name) -> printfn "%s -- %s" year name)The result is:
1943 -- Academy Award for Best Director
1943 -- Academy Award for Best Picture
1943 -- Academy Award for Best Screenplay
So that's Freebase. Lots of good information, both useful and frivolous.
More on how to use the Freebase type provider.
We've seen how FsCheck can be used to generate test data. Well, you can also get the same affect by getting data from Freebase, which makes the data much more realistic.
Kit Eason showed how to do this in a tweet, and here's an example based on his code:
let randomElement =
let random = new System.Random()
fun (arr:string array) -> arr.[random.Next(arr.Length)]
let surnames =
FreebaseData.GetDataContext().Society.People.``Family names``
|> Seq.truncate 1000
|> Seq.map (fun name -> name.Name)
|> Array.ofSeq
let firstnames =
FreebaseData.GetDataContext().Society.Celebrities.Celebrities
|> Seq.truncate 1000
|> Seq.map (fun celeb -> celeb.Name.Split([|' '|]).[0])
|> Array.ofSeq
// generate ten random people and print
type Person = {Forename:string; Surname:string}
Seq.init 10 ( fun _ ->
{Forename = (randomElement firstnames);
Surname = (randomElement surnames) }
)
|> Seq.iter (printfn "%A")The results are:
{Forename = "Kelly"; Surname = "Deasy";}
{Forename = "Bam"; Surname = "Br?z?";}
{Forename = "Claire"; Surname = "Sludden";}
{Forename = "Kenneth"; Surname = "Kl?tz";}
{Forename = "?tienne"; Surname = "Defendi";}
{Forename = "Billy"; Surname = "Paleti";}
{Forename = "Alix"; Surname = "Nuin";}
{Forename = "Katherine"; Surname = "Desporte";}
{Forename = "Jasmine"; Surname = "Belousov";}
{Forename = "Josh"; Surname = "Kramarsic";}
The code for this section is available on github.
On the other extreme from Freebase is the World Bank Open Data, which has lots of detailed economic and social information from around the world.
The setup is identical to Freebase, but no API key is needed.
// sets the current directory to be same as the script directory
System.IO.Directory.SetCurrentDirectory (__SOURCE_DIRECTORY__)
// Requires FSharp.Data under script directory
// nuget install FSharp.Data -o Packages -ExcludeVersion
#r @"Packages\FSharp.Data\lib\net40\FSharp.Data.dll"
open FSharp.Data
let data = WorldBankData.GetDataContext()With the type provider set up, we can do a serious query, such as:
"How do malnutrition rates compare between low income and high income countries?"
// Create a list of countries to process
let groups =
[| data.Countries.``Low income``
data.Countries.``High income``
|]
// get data from an indicator for particular year
let getYearValue (year:int) (ind:Runtime.WorldBank.Indicator) =
ind.Name,year,ind.Item year
// get data
[ for c in groups ->
c.Name,
c.Indicators.``Malnutrition prevalence, weight for age (% of children under 5)`` |> getYearValue 2010
]
// print the data
|> Seq.iter (
fun (group,(indName, indYear, indValue)) ->
printfn "%s -- %s %i %0.2f%% " group indName indYear indValue)The result is:
Low income -- Malnutrition prevalence, weight for age (% of children under 5) 2010 23.19%
High income -- Malnutrition prevalence, weight for age (% of children under 5) 2010 1.36%
Similarly, here is the code to compare maternal mortality rates:
// Create a list of countries to process
let countries =
[| data.Countries.``European Union``
data.Countries.``United Kingdom``
data.Countries.``United States`` |]
/ get data
[ for c in countries ->
c.Name,
c.Indicators.``Maternal mortality ratio (modeled estimate, per 100,000 live births)`` |> getYearValue 2010
]
// print the data
|> Seq.iter (
fun (group,(indName, indYear, indValue)) ->
printfn "%s -- %s %i %0.1f" group indName indYear indValue)The result is:
European Union -- Maternal mortality ratio (modeled estimate, per 100,000 live births) 2010 9.0
United Kingdom -- Maternal mortality ratio (modeled estimate, per 100,000 live births) 2010 12.0
United States -- Maternal mortality ratio (modeled estimate, per 100,000 live births) 2010 21.0
More on how to use the World Bank type provider.
So you're putting all these suggestions into practice. You're parsing your web logs with FParsec, extracting stats from your internal databases with the SQL type provider, and pulling down external data from web services. You've got all this data -- what can you do with it?
Let's finish up by having a quick look at using F# for data science and machine learning.
As we have seen, F# is great for exploratory programming -- it has a REPL with intellisense. But unlike Python and R, your code is type checked, so you know that your code is not going to fail with an exception halfway through a two hour processing job!
If you are familiar with the Pandas library from Python or the ?tseries' package in R, then you should take a serious look at Deedle, an easy-to-use, high quality package for data and time series manipulation. Deedle is designed to work well for exploratory programming using the REPL, but can be also used in efficient compiled .NET code.
And if you use R a lot, there's an R type provider(of course). This means you can use R packages as if they were .NET libraries. How awesome is that!
There's lots of other F# friendly packages too. You can find out all about them at fsharp.org.
Phew! That was a long list of examples and a lot of code to look at. If you've made it to the end, congratulations!
I hope that this has given you some new insights into the value of F#. It's not just a math-y or financial language -- it's a practical one too. And it can help you with all sorts of things in your development, testing, and data management workflows.
Finally, as I have stressed throughout this series, all these uses are safe, low risk and incremental. What's the worst that can happen?
So go on, persuade your team mates and boss to give F# a try, and let me know how it goes.
After I posted this, Simon Cousins tweeted that I missed one -- I can't resist adding it.
@ScottWlaschin 27: balance the generation schedule for the uk power station fleet. seriously, the alternative to #fsharp was way too risky
— Simon Cousins (@simontcousins) April 25, 2014You can read more about Simon's real-world of use of F# (for power generation) on his blog. There are more testimonials to F# at fsharp.org.